Linked by Thom Holwerda on Thu 8th Nov 2012 20:54 UTC, submitted by Elv13
Thread beginning with comment 541554
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Because because because, GNOME devs also have becauses you know.
Yes, but opinions don't hold equal weight merely because they are equally fervent.
By welcoming GTK+'s rise to popularity as a general toolkit used by many different desktops, the developers also implicitly accepted responsibility to manage GTK+'s development wisely.
As a user, my only responsibilities are to be polite, to avoid acting entitled, to report bugs, and to choose a desktop where the developers views on good UI design are not diametrically opposed to mine.
I have done all of those. I am not a GNOME user and my issue isn't with GNOME. It's with the GNOME devs abusing the power over other desktops (like LXDE) that maintainership of GTK+ grants based on those other desktops' views of their formerly responsible behaviour.
Edited 2012-11-09 02:37 UTC





Member since:
2010-01-21
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.
...because, if said breakages do exist, I never encounter them. This stuff actually affects the end user.
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