having targetted both Qt api and the new Libadwaita api, this is going to happen more and more. the new GTK APIs are a pain in the ass and it’s pretty clear they only target GNOME, and since GNOME 4, there’s been no guarantee of API backwards compatiblity. it’s a nightmare.
they took all the wrong lessons from NodeJS and have slowly been making themselves irrelevant outside of bleeding edge and rolling release distros. from the GNOME devolopers i’ve talked to, they don’t see this as any of their concern because they’re still the leading desktop environmnet, however, more and more i see Qt becoming the general development target, and i don’t see that changing unless GNOME starts treating Gtk as something GNOME is built around rather than as something that makes developing GNOME apps easy. KD, and LXDE together make up more of the user desktops than GNOME, XFCE, and Cinnamon, and GNOME is the only one of those that even supports the latest versions of Gtk.
they’ve been alienating users for 15 years now, and they refuse to change course. i don’t think it will be long until KDE is the leading desktop environment purely because GNOME refuses to treat critiques of their desktop as legitimate concerns from frustrated users rather than as opportunities to create something better. it will eventually get to a point where only the people who treat Richard Stallman as a religious figure will still be around
Yeah, the thing that bothers me about GNOME isn’t the design, that’s not for me but whatever, it’s the attitude the project takes to collaboration and refusing to compromise on anything that would be useful for literally every other desktop in stuff like Wayland protocols
yuuup! then when other devs get fed up and align themselves with other toolkits, GNOME’s adherents complain about the fracturing nature of desktop. and it’s like… self reflect! realize who fractured it! change your attitude!
having targetted both Qt api and the new Libadwaita api, this is going to happen more and more. the new GTK APIs are a pain in the ass and it’s pretty clear they only target GNOME, and since GNOME 4, there’s been no guarantee of API backwards compatiblity. it’s a nightmare.
So what you’re saying is gnome is a self solving problem
they took all the wrong lessons from NodeJS and have slowly been making themselves irrelevant outside of bleeding edge and rolling release distros. from the GNOME devolopers i’ve talked to, they don’t see this as any of their concern because they’re still the leading desktop environmnet, however, more and more i see Qt becoming the general development target, and i don’t see that changing unless GNOME starts treating Gtk as something GNOME is built around rather than as something that makes developing GNOME apps easy. KD, and LXDE together make up more of the user desktops than GNOME, XFCE, and Cinnamon, and GNOME is the only one of those that even supports the latest versions of Gtk.
they’ve been alienating users for 15 years now, and they refuse to change course. i don’t think it will be long until KDE is the leading desktop environment purely because GNOME refuses to treat critiques of their desktop as legitimate concerns from frustrated users rather than as opportunities to create something better. it will eventually get to a point where only the people who treat Richard Stallman as a religious figure will still be around
Yeah, the thing that bothers me about GNOME isn’t the design, that’s not for me but whatever, it’s the attitude the project takes to collaboration and refusing to compromise on anything that would be useful for literally every other desktop in stuff like Wayland protocols
yuuup! then when other devs get fed up and align themselves with other toolkits, GNOME’s adherents complain about the fracturing nature of desktop. and it’s like… self reflect! realize who fractured it! change your attitude!