Linked by Thom Holwerda on Thu 8th Nov 2012 20:54 UTC, submitted by Elv13
Permalink for comment 541616
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2005-07-06
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.
We are several point releases into GTK 3.x now. A Minor release means you maintain backwards compatibility. The API will never 'settle down'.
It's OK. That's happening.
No, they don't. People in userspace outside the kernel moved from Linux 2.4 to 2.6 with barely a murmur. Stuff worked.
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.