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 541551
To read all comments associated with this story, please click here.
...
by Hiev on Fri 9th Nov 2012 00:45 UTC
Hiev
Member since:
2005-09-27

Dear whiners:

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. If you wan't to customise it and make themes and whatever, you will have to waith to the API settles down or update your theme with every release.

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.

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

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.

Edited 2012-11-09 00:59 UTC

Reply Score: -1

RE: ...
by ssokolow on Fri 9th Nov 2012 01:04 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

RE[2]: ...
by Hiev on Fri 9th Nov 2012 02:20 in reply to "RE: ..."
Hiev Member since:
2005-09-27

Because because because, GNOME devs also have becauses you know.

Edited 2012-11-09 02:21 UTC

Reply Parent Score: 1

RE: ...
by segedunum on Fri 9th Nov 2012 13:32 in reply to "..."
segedunum Member since:
2005-07-06

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.

...you 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: ...
by TechGeek on Fri 9th Nov 2012 16:05 in reply to "..."
TechGeek Member since:
2006-01-14

Dear dumb ass gnome developers:

The freshman software engineers in my college learn to ask for user requirements before they start coding. How about doing the same. There is no point wasting your time if no one wants to use the crap you produce. And your stupid bar across the top is a waste of space if I can't alter it. You fail at UI design.

Reply Parent Score: 3

RE[2]: ...
by Hiev on Fri 9th Nov 2012 16:08 in reply to "RE: ..."
Hiev Member since:
2005-09-27

Dear ignorant troll:

I use GNOME Shell just fine and I'm so productive with it, the fact that you don't share the same opinion doesn't mean we all dislike it.

Is called, "Get the facts 101" do they teach that in your college?

Edited 2012-11-09 16:09 UTC

Reply Parent Score: -1

RE: ...
by gilboa on Fri 9th Nov 2012 18:40 in reply to "..."
gilboa Member since:
2005-07-06

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


Bullshit.
I maintain a fairly large out of tree kernel project that covers everything from kernel file management to networking and memory / cpu management (and includes a number of out-of-tree drivers).
In the past 10 years I seldom spent more than 1-2 hours porting my code to a new kernel release.

Care to prove wrong?

- Gilboa

Reply Parent Score: 7

RE[2]: ...
by Hiev on Fri 9th Nov 2012 18:42 in reply to "RE: ..."
Hiev Member since:
2005-09-27

Good for you Gilboa, I was thinking the same, but the only it brokes are mostly closed source libraries that cannot be recompiled, yes, I had my doubts in that statement, so I take it back.

Reply Parent Score: 3