I wonder how high those structural problems are on #Gnome's roadmap.
-
-
Miroreplied to Natasha Nox πΊπ¦π΅πΈ last edited by
@Natanox I wanted to complain, because I love Gnome, but then I realized that my system regularly suffered from crashes lately, so... feel yah!
-
Natasha Nox πΊπ¦π΅πΈreplied to Miro last edited by
@miro I do use and love it as well, but those problems are bugging me out (quite literally).
-
TheEvilSkeletonreplied to Natasha Nox πΊπ¦π΅πΈ last edited by
> due to extensions
That's unfixable in GNOME. It's like blaming VS Code when an extension is causing it to behave badly.
As for the second one, you are free to design mockups and/or contribute the options yourself. There are bigger problems to solve, in my opinion. Wellbeing is one of them.
-
Natasha Nox πΊπ¦π΅πΈreplied to TheEvilSkeleton last edited by
@TheEvilSkeleton Wellbeing features are more important than including core functionalities in places people expect them? Mmh, if you think soβ¦
Can you elaborate "unfixable"? (Extension) Instability is one of the biggest problems Gnome suffers from in my opinion.
-
TheEvilSkeletonreplied to Natasha Nox πΊπ¦π΅πΈ last edited by
> Wellbeing features are more important than including core functionalities in places people expect them? Mmh, if you think soβ¦
Define core functionalities? I'm already using Wellbeing so I consider that a core functionality already (I use GNOME OS).
> Can you elaborate "unfixable"? (Extension) Instability is one of the biggest problems Gnome suffers from in my opinion.
If an extension crashes GNOME, it's outside of GNOME's control. Same way a VS Code extension crashing VS Code doesn't make it a VS Code problem.
-
Natasha Nox πΊπ¦π΅πΈreplied to TheEvilSkeleton last edited by
@TheEvilSkeleton There are ways around that, so extensions of something can gracefully crash without the core being dragged down with it. Often it's done via some kind of API.
Given this is about an operating systems' graphical interface it's very much an imperative to run as solid as possible. There has to be a way.
-
Miroreplied to Natasha Nox πΊπ¦π΅πΈ last edited by
@Natanox yeah, me too, even though I blamed NixOS for the issues. Sometimes I like to tinker, but I don't want to be forced to.
-
Natasha Nox πΊπ¦π΅πΈreplied to Miro last edited by
@miro A Gnome Foundation member who replied to the meme got *really* weird prioritiesβ¦ and apparently argues that preventing extensions from crashing Gnome is impossible. Which is an interesting take, no wonder nothing improves in this regard. π§ https://social.treehouse.systems/@TheEvilSkeleton/113860620692392792
-
melzerreplied to Natasha Nox πΊπ¦π΅πΈ last edited by
@Natanox @TheEvilSkeleton
It is the same problem as with the old Firefox Extensions, if you are old enough to remember the pre-webextension times: An extension in GNOME is just monkey patching javascript into the process. If that goes wrong, tough luck.Of course: GNOME could go the same way as Firefox and present an extension API but I can already hear the cries as this would definitely not allow for many things currently possible.
So which do you prefer?
-
Natasha Nox πΊπ¦π΅πΈreplied to melzer last edited by
@melzer @TheEvilSkeleton Would the existence of an 'official' extension API prevent the existence of a "Monkey Patcher"?
Like I said⦠it's about a critical part of every computer. When Gnome goes down it takes everything you do with it without exception, and without deep system knowledge the only way to recover might be a full reboot. It would be an improvement for extension devs as well, since right now every major update causes every extension to break. It's an awful situation all around.