4 ms·
Gnome keeps making big changes that hurt users and app developers, at least in the short term. (Presumably in pursuit of the Gnome developers' vision.) If you
by nycticorax 4y ago
Gnome keeps making big changes that hurt users and app developers, at least in the short term. (Presumably in pursuit of the Gnome developers' vision.) If you do that often enough, users and app developers find themselves basically in a continual state of pain, always adapting to the latest change. But the Gnome developers either don't recognize this or don't care (or care more about other things), because they keep doing it. Thus: "My way or the highway".
I got tired of it, and the relentless dumbing-down of everything, and switched to KDE (in the form of Kubuntu). It's nice! And the developers seem to understand that it mostly works OK, and they don't need to force a UI paradigm shift on you (and their third-party app developers) every few years.
- deleted 4y ago[deleted]
- lmedinas 4y agoI agree and the constant API changes over the last years on GTK+/Glib and GNOME libraries hurt users and developers.
- tristan957 4y agoWhat do you mean constant API changes? GTK 3 existed for what, 10 years? GLib hasn't had an API break in how long?
- Gigachad 4y agoLinux devs will ignore a feature going obsolete and complain 10 years later when it's removed. It doesn't matter how long you give because they were never actually working on it in the mean time.
- the_why_of_y 4y agoGLib 2.0 was released on 2002-03-08. There's not a whole lot you'd be using on the desktop that's maintained ABI for longer; mainly X11 libraries, glibc, NSS, zlib, libxml2 (latter one is also a GNOME project). (Anything using C++ would have a libstdc++.so.6 related ABI break at a later date.)