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.
Thread beginning with comment 541616
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: ...
by segedunum on Fri 9th Nov 2012 13:32 UTC in reply to "..."
Member since:

GNOME devs made it clear that they weren't interested in maintaining the theme engine for multiporposes, just for the needs of the default theme, they said this since day one.

No, they didn't. This also goes way, way beyond the theming engine because it's become very clear that GTK is a rapidly moving target. will have to waith to the API settles down....

We are several point releases into GTK 3.x now. A Minor release means you maintain backwards compatibility. The API will never 'settle down'.

...or contribute to other DE like KDE or XFCE, cause, it is a free world.

It's OK. That's happening.

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

No, they don't. People in userspace outside the kernel moved from Linux 2.4 to 2.6 with barely a murmur. Stuff worked.

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

While that kind of thing is regrettable it had to be done because QML could be better supported, Plasmoids made more reliable as a result and more could be integrated into Qt itself as a stable target for everyone. Divergence in that sense is just not beneficial.

GTK is currently the complete opposite of that. It is breaking for no good reason every other point release with absolutely no release policy other than 'We felt like it'. People took shots at KDE 4 but it never did anything like this. They started off with a basic .0 release and moved solidly from there with API and ABI compatibility.

When you have no developers and you are pissing off the ones you have, and you are pissing off your users because of said developer breakage then you are dead. Have fun.

Reply Parent Score: 6

v RE[2]: ...
by Hiev on Fri 9th Nov 2012 14:25 in reply to "RE: ..."
RE[3]: ...
by segedunum on Fri 9th Nov 2012 14:55 in reply to "RE[2]: ..."
segedunum Member since:

WTF? Go read the mailing list you ignorant troll

Read what mailing list you utter twit? Theming is a part of GTK, or at least it is supposed to be. It's, you know, a graphical toolkit. The default Gnome theming is something else. That's where these problems are coming from. A toolkit, GTK, is enforcing Gnome preferences on everyone else.

Application developers are whiners. Pure brilliance. Pure ignorance. Troll..... Hilarious.

Edited 2012-11-09 14:59 UTC

Reply Parent Score: 3