4 ms·
The slowness was very apparent for me too. I used to keep restarting the shell (Alt F2, then r) to get it back to normal speeds(this doesn't close the running a
by kkaranth 8y ago
The slowness was very apparent for me too. I used to keep restarting the shell (Alt F2, then r) to get it back to normal speeds(this doesn't close the running applications).
In Wayland, they removed this shortcut. I've since switched to KDE.
- devxpy 8y agoYou can blame js for that. It's known as the famous gnome memory leak.
- pjmlp 8y agoModern KDE also uses JS. So I guess Qt's implementation is of better quality.
- de_watcher 8y agoQt projects tend to use js as the js was originally intended: small one-liners (in this case, to glue some QML together).
- majewsky 8y ago> In Wayland, they removed this shortcut. I'm usually not one to come to Gnome's defence, but it's very likely they did not really have any choice there. In Wayland, the compositor is the parent process of the entire session, so you cannot restart it willy-nilly. That's a design choice made by the Wayland protocol, not by the Gnome devs.
- kkaranth 8y agoThe real problem was that the shell got slower over time. If that was fixed, the choice of Wayland vs. X wouldn't bother me.