The shell certainly has issues. They need to stop fighting with JavaScript (https://ptomato.wordpress.com/2018/11/06/taking-out-the-garbage/ …) and build a native version to get the reliability and memory use under control.
For example I’ve had nothing but trouble from extensions so given up using any. I feel like GNOME should be able to take the project where they want to without being limited by upstream concerns, as an outsider it seems this is how many things happen anyway.
-
-
This discussion has made me consider re-evaluating some DE shells that are more aligned with my desire for a lighter weight, JS-free shell. I don't think it's fair to be complaining about something when there are other options to try.
-
You should certainly use what fits your preferences.However keep in mind that my whole point was that the fact that we use JS is not the source of preceived bloat/resource hungryness.The problem is elsewhere and a bunch of us are determined to address it: https://wiki.gnome.org/Hackfests/Performance2018 …
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.