OpenSuSE (read: open-zus) 42.1 Leap has been released. I remember that it was 10.1 at the first time I came to Linux, must be 9 or 10 years ago. My personal coupling with OpenSuSE had once been disrupted by the appearance of Ubuntu trend. Then the journey was started. I came through Ubuntu, Fedora, Gentoo (not for too long), even FreeBSD & Solaris (when it was free); now I come back to OpenSuSE.
Why? There are many reasons:
1. Its well polished desktop environment
I returned using OpenSuSE from its 13.2. I'm a software developer and my daily work accompanied with numerous development tools and environments: python, C/C++/Cuda, Java, even PHP and Ruby. For me, personally, OpenSuSE + KDE is the most usable and productive environment for its comprehensive tools collection and usable environment. I have seen many people around complained about its substandard stability; but for me it's quite OK, experienced by hours of heavy development activities without disruption.
2. Its release schedule and rock-solid base
I couldn't say that I'm satisfied by the release schedule of the major distributions. Fedora release a new version every 6 months and life cycle is 13 months. Shorter life cycle means you have to upgrade your system more frequently. Not only that, every time it comes with several bugs at beginning. Fedora is the testbed for bleeding-edge techs and though it has more and more cool features, it's remarkably unstable and not suitable for my production environment.
What about Ubuntu? Ubuntu has the best support and stability for their LTS release; but it's 2-years release cycle. Sometimes I find some packages are outdated. But it's not the most important issues; actually I hate Unity, and I prefer .rpm system over .deb . I'm sorry for the irrelevant arguments.
What about OpenSuSE? The combination of SLES base with its enterprise-level stability and the novel features of upstream desktop components suite me the best. With 12-months cycle for minor release and 36 months cycle for major release, I don't need to do major upgrade too frequently while desktop applications are kept updated.
I know it's pretty stupid to say it but arguments are just arguments; sometimes you do something just because you feel like to do it. And yes I like the gecko, personally :)
It's pretty kool.
Thursday, November 12, 2015
Tuesday, November 10, 2015
Monday, November 9, 2015
[ Coding ] Gvim's annoying window gap....
Anyone who use gvim on kde platform would be upset by the small annoying gap between gvim window and the screen border.
How to solve it? Very simple, right-click on the window border -> select "special application setting"
and it's done...
[ Coding ] Coding conventions for C++ and Python.
< Update > PHP style guideline
It's annoying that something I look at my code written for quite a long time and couldn't understand why I had once written that mess. I know it sounds stupid, but most of my code alterations are just name changing. Damn...
Just mention some conventions here to memorize them. I'd better follow them strictly and consistently.
Decided to use CERN coding style. I mean, Google Coding Style Guideline is the first result shown by Google, and I guess most of developer are using it. So, I decided to cook my code in a different way...
> Python: it's apparent that PEP8 is the first law to obey. Further reading:https://twiki.cern.ch/twiki/bin/view/BEABP/PythonStyleGuide
> C++:
http://pst.web.cern.ch/PST/HandBookWorkBook/Handbook/Programming/CodingStandard/c++standard.pdf
> PHP: i have recently found that PHP conventions vary among frameworks and projects. God damn it. Frankly, following the Apache's PHP Style Guideline is better than changing the way of coding every single times...
http://svn.apache.org/repos/asf/shindig/attic/php/docs/style-guide.html
> Ruby: proposed to be updated later. The problem is that I do not frequently use it...
Anw, need an idea for a bb10 app... Thinking about an ebook reader ...
It's annoying that something I look at my code written for quite a long time and couldn't understand why I had once written that mess. I know it sounds stupid, but most of my code alterations are just name changing. Damn...
Just mention some conventions here to memorize them. I'd better follow them strictly and consistently.
Decided to use CERN coding style. I mean, Google Coding Style Guideline is the first result shown by Google, and I guess most of developer are using it. So, I decided to cook my code in a different way...
> Python: it's apparent that PEP8 is the first law to obey. Further reading:https://twiki.cern.ch/twiki/bin/view/BEABP/PythonStyleGuide
> C++:
http://pst.web.cern.ch/PST/HandBookWorkBook/Handbook/Programming/CodingStandard/c++standard.pdf
> PHP: i have recently found that PHP conventions vary among frameworks and projects. God damn it. Frankly, following the Apache's PHP Style Guideline is better than changing the way of coding every single times...
http://svn.apache.org/repos/asf/shindig/attic/php/docs/style-guide.html
> Ruby: proposed to be updated later. The problem is that I do not frequently use it...
Anw, need an idea for a bb10 app... Thinking about an ebook reader ...
Subscribe to:
Posts (Atom)


