Linked by Thom Holwerda on Thu 8th Nov 2012 20:54 UTC, submitted by Elv13
Gnome "Theme development is a tedious and difficult task, and for the GTK devs to be so careless in breaking their API at every turn disrespects the many hours people put into making themes for it. [...] I was given to believe that this breakage stems from a Microsoft-like climate of preventing users from customizing their systems, and deliberately breaking the work of others so that your 'brand' is the best. Anytime I hear the word 'brand' being used in Linux, I know something valuable is being poisoned." I find the tone of this one a bit too harsh and overly negative at times, but his point still stands.
Permalink for comment 541554
To read all comments associated with this story, please click here.
RE: ...
by ssokolow on Fri 9th Nov 2012 01:04 UTC in reply to "..."
ssokolow
Member since:
2010-01-21

The engine still needs optimization and they are working on it, if you don't like it, you can always fork it, or contribute to other DE like KDE or XFCE, cause, it is a free world.


XFCE is based on GTK+, as is LXDE. The only DEs which aren't being forced to choose between dead code (GTK+ 2) and having GNOME devs yank them around like marionettes (GTK+ 3) are KDE and Razor-Qt and only when used without programs like VMWare and GIMP which use GTK+ for their GUIs.

BTW, the Linux kernel break a bunch of stuff every with release, and I don't see you bitching about it.


...because, if said breakages do exist, I never encounter them. This stuff actually affects the end user.

KDE 4 deprecated all the python, ruby, etc. plasmoids for the sake of QML and javascript and I don't see you whinning eather.


Because I was unaware of it... Great! Now where am I gonna flee to when Weston implements client-side window decorations?

Maybe I'll still be able to use KWin with no other KDE apps when that eventually becomes an issue.

Edited 2012-11-09 01:07 UTC

Reply Parent Score: 5