And because Gnome still lets every extension monkey-patch code right into the shell your whole desktop may crashes in the middle of your work. Especially if the extension devs aren’t monitoring changes in Gnome 24/7.
Happened to me 3 times before I moved to KDE. Which I very much dislike in comparison, but it’s just way more stable. Couldn’t go without extensions in Gnome either because of the very smooth-brained decision to replace the tray icons with their own backend, so any app not supporting their way of doing it either disappears into the void or has their tray icon submenu inaccessible.
Ugh. I love the UI/UX of Gnome, but in terms of stability and compatibility they screwed up phenomenally.
I feel like it would be easier for everyone that Gnome team made a more stable way for extensions to interact and change the system, but that goes against their philosophy and unified vision. Gnome seems to despice the extensions that so many of their users think are required for sensible use of Gnome desktop.
<rant>
The funniest thing about it is the reason why they won’t create an extension API: developer freedom. Because some extensions would stop working with an API, according to them. (Which is a damn weak reason, nothing prevents them from keeping the unstable patch path open and let users decide if they want to install potentially dangerous extensions or just those marked as “safe”, i.e. API-only).
Despite being told they actively decided against such an API I of course was still hit with the “just build it yourself and make a PR” line. Yeah, sure, who doesn’t want to waste dozens to hundred of hours for an already rejected concept?
That’s the same people who brought us libadwaita, which is in fact so well known for developer freedom that Linux Mint saw it as a necessity to fork it into libadapta to reintroduce more freedom.
</rant>
God I’m so annoyed by this. Gnome’s organisational structure screws the whole desktop. At least that’s something they’re partially aware of…
And because Gnome still lets every extension monkey-patch code right into the shell your whole desktop may crashes in the middle of your work. Especially if the extension devs aren’t monitoring changes in Gnome 24/7.
Happened to me 3 times before I moved to KDE. Which I very much dislike in comparison, but it’s just way more stable. Couldn’t go without extensions in Gnome either because of the very smooth-brained decision to replace the tray icons with their own backend, so any app not supporting their way of doing it either disappears into the void or has their tray icon submenu inaccessible.
Ugh. I love the UI/UX of Gnome, but in terms of stability and compatibility they screwed up phenomenally.
I feel like it would be easier for everyone that Gnome team made a more stable way for extensions to interact and change the system, but that goes against their philosophy and unified vision. Gnome seems to despice the extensions that so many of their users think are required for sensible use of Gnome desktop.
<rant> The funniest thing about it is the reason why they won’t create an extension API: developer freedom. Because some extensions would stop working with an API, according to them. (Which is a damn weak reason, nothing prevents them from keeping the unstable patch path open and let users decide if they want to install potentially dangerous extensions or just those marked as “safe”, i.e. API-only).
Despite being told they actively decided against such an API I of course was still hit with the “just build it yourself and make a PR” line. Yeah, sure, who doesn’t want to waste dozens to hundred of hours for an already rejected concept?
That’s the same people who brought us libadwaita, which is in fact so well known for developer freedom that Linux Mint saw it as a necessity to fork it into libadapta to reintroduce more freedom. </rant>
God I’m so annoyed by this. Gnome’s organisational structure screws the whole desktop. At least that’s something they’re partially aware of…