Seriously, it will stabilise eventually. Without these changes, we wouldn't have some of the best features (like the new Cairo stuff and CSS styles). These developers sound like they'd rather hack on a 1990s desktop than actually try and make something the least bit modern.
Judging by your comment, i am guessing a big fat ZERO... They break themes on every point release, it is hugely annoying for anyone trying to maintain multiple themes (for others to use). Themes often don't break 'gracefully' and your left to figure out what happened... But of course, this not only affects people whom are providing themes, but also end users... Sure, people using a 6month release-cycle distro, probably don't get bitten hard, since they will be re-installing anyway for the next release (unless they dist-upgrade), but for those of us who are using rolling release model - it blows; you update (even if not a gnome user) and your gtk3 apps are borked...
so i don't think we are discussing a 90's desktop vs. a modern one - the 90s desktop doesn't even come into question - ie: it's the modern one that is constantly breaking (and it's been this for what (?) a year and a half of this now (?)... So in terms of stabilizing - it does beg the question ~ When is it going to stablize??? 2yrs, maybe 3yrs?).
I dropped all of my themes and only maintain my own theme, for my own machines. If Gnome hadn't have continued to break theming constantly, i would probably be maintaining 5-6 themes right now :\ So maybe you don't see this as an issue ~ but it is, they need to iron out theming and provide a stable gtk+ that doesn't break on every update.
...and as a side note: ironically, the only theme they maintain / that doesn't break is probably in the top 5 crappiest themes ever conceived of (Adwaita). hilarious.
I thought I'd post the above for anyone interested.Quote:
This post sounds a bit like “Hey look, I ran a simple command that showed things are slow. Why is nobody doing anything about it?!” aka the Phoronix way of talking about software.
I personally don’t consider my login time anything worth working on. There’s so many more important things to be working on, like for example getting GNOME to run on an iPhone (or at least a Samsung Galaxy) with software that’s superior to what’s running there now. When that’s done, I might look into your performance issues.
What was really funny was that Benjamin then made the completely reasonable argument about developer resources but made the mistake of thinking that everyone else thinks as he does about start-up times. In particular that Jean-Francois wouldn't spend his time getting pitivi to start faster. To which Benjamin found the contrary to be the case.
Oh please support Qt styles with future versions of GTK...... it is so silly to have to use oxygen-gtk to have same look apps.... well or a gtk style on both Qt and gtk...... which is strange in KDE. The opposite is very welcome :). And thank you very much to oxygen-gtk authors, they changes my KDE experience, really.
GTK+ 3.0 was released around ~Feb 2011. In 2 days we will be in 2013. That's almost 2 years of constant breakage on every damn release!
You need to intruduce breakage and do a complete overhaul. Totally fine. That's what 3.0 is supposed to be for! 3.0 introduces breakage with 2.x, but the rest of the 3.x serious should not have any more breakage. You should be compatible going forward until several years down the line when you go to 4.x.
Nearly 2 years of breakage, instability and utter lack of documenting the changes is absurd.