Every time GNOME updates to a new version—it feels like it happens every few months—it breaks all my extensions.
I rely on a number of extensions to get GNOME Shell to behave the way I want it to:
- Argos, so that I can display the output of commands I need to monitor
- Dash to Dock, to have a nicely working dock
- Pop Shell, for window tiling
- Tray Icons, so I can see what, e.g., Megasync is doing, without having a window open
- GSConnect, to interface with my phone
- Multi Monitors addon, since I use more than one monitor
… and more, like those which add search functionality to the activities overview search.
The trouble is, every time GNOME updates to a new version, basically all extensions break catastrophically, and can no longer be enabled.
For me, that suddenly makes GNOME almost unusable, since nothing is behaving the way I need it to.
Does GNOME have to change its entire codebase every six months, forcibly invalidating every extension that used to work with it? Do all these extensions really cease to work every few months, as a result?
I remember when Firefox switched its extensions system, and it invalidated all of the extensions that previously used to work with it. That was a major inconvenience, but at least then, the extension developers had lots of advance warning, where they could rewrite their extensions to fit the new API. But more importantly, it only happened once. (In recent memory, that is.) In contrast, GNOME Shell seems to do this all the time, and it’s really annoying.
I know I could hack my system to pin GNOME shell to a particular version, but this would probably affect the rest of the ecosystem, as well, and would be a pain to have to maintain.
Isn’t there anything that can be done about this? Like, automatically mark extensions as compatible with the latest version, unless their tests fail? It seems like there should be a better solution, no?