I’ve been using Fedora for a couple of months now, and have been loving it. Very soon after I jumped into this community (among other Linux communities) and started laughing at all the people saying “KDE rules, GNOME drools,” and “GNOME is better, KDE is for babies.” But then I thought, “Why not give KDE a try? The worst that happens is I go back to using GNOME.”
Now I get it. The level of customization is incredible, it’s way faster than GNOME, and looks beautiful too. At this point, I’m not going back.
I’ll happily contribute to the playground fight over desktop environments. KDE rules, GNOME drools.
I’ve also been a Gnome user for a while, but i am looking forward to plasma 6 as well. I highly doubt I’ll make any sort of switch, but I’ve never had a good time running plasma 5 so i would love to like kde more. Wayland by default is going to benefit gnome too since it’ll put more priority on bugs and lack of support that is still somewhat common among the less desktop-tied apps.
(My Plasma 5 woes have been on multiple devices, multiple times over multiple years, with and without basic customization. i was basically never able to go a day without some sort of major shell crash. I got way too familiar the the command sequence to restart the desktop ui)
I do find KDE to be a bit info dense and it doesn’t look like 6 is changing that aspect of things (at least by default), but it does look a bit less busy at least. I also never like basically anything about classic windows UI, layout, or task flows so KDE leaning into those just doesn’t work well for me. That said, while i like gnome being more minimal, i do wish it had a bit more capability to expose hidden/nested options more easily than requiring extension installs.
I’m similarly excited about cinnamon 6. A bit unfortunate (and understandable given its goals and usage share) it is still X11, but there’s a lot about it that demonstrates a solid middle ground between gnome and KDE.
I am usually on the pro-Wayland side but with GNOME and KDE the Wayland implementations are fairly independent. That means that your statement that KDE going “Wayland by default is going to benefit gnome too since it’ll put more priority on bugs” is watered down somewhat.
Fixing bugs in the KDE compositor / display server ( KWin ) will not necessarily address bugs or missing functionality in GNOME ( Mutter ). A lot of what they share is also shared with Xorg ( libinput, libdrm, KMS, Mesa ).
On the application side, apps lean heavily on the toolkit libraries. KDE apps are built with Qt and GNOME apps are built with GTK. Fixing Qt bugs may not improve the quality of GTK and vice versa.
Smaller projects will share more infrastructure. Many other environments are using Wlroots as a compositor library for example. Fixing bugs there will benefit them all but again is independent of KDE and GNOME.
Your point is still valid though. For one thing, the larger the Wayland user base, the greater the number of use cases the Wayland protocol itself will be adapted to address and the more testing and development everything in the Wayland ecosystem will get.
Over time, one benefit of multiple implementations will probably be code quality. Apps that run well in multiple environments are well implemented and the same is true of environments that provide the necessarily features to a large body of apps. In that way, more bugs will be found and fixed in all environments.