Well you compare a heavy JavaScript based DE (Gnome) with a C++ one (KDE, with Qt). That's also unfair.
But if you try i3 or OoenBox, they are way faster
But if you try i3 or OoenBox, they are way faster
> Canonical's write-up of the work done to improve GNOME is also interesting for the long list of what didn't work and how wrong some of the developers' initial assumptions were—especially regarding GNOME's use of JavaScript. > It turns out JavaScript had next to no effect on performance. So sorry JavaScript haters, but "assuming that JavaScript is slower than everything else written in C" is evidently a bad assumption
As this is really hard to fix they fixed this by constantly running the gc in December 2018. This worked OK but didn't fix the issue for all until 2019.
Does making it broken for 8 years so usability comes 8 years late count as making it slow.
But those are just window managers no? You can run them alongside KDE or Gnome.
It's questionable how much value is added by running a plasma session over simply running KDE apps and services.