You need to understand the difference between the quality of Wayland itself and the specific implementation of a compositor but you don’t. “Plasma’s Wayland port is incomplete, so Wayland developers should consider it a failed project and work on X11 instead” as an attitude just makes zero sense.
Now you’re using a complete strawman here. I never said it’s because the Wayland port is incomplete but because I think it doesn’t work on key software in 2023. Wayland had its first release in 2008, that’s 15 years ago, that’s a long time and if there’s still questions about its maturity then that’s a fatal flaw. Maybe it even says something if downstream developers have to port it instead of being able to just switch out X11, but of course that might just as well be a quirk of X11.
You initially said that most applications in general are not compatible with Wayland and that’s untrue. If you personally happen to mainly use only outdated Electron applications, that’s your problem but doesn’t reflect of the state of the wider ecosystem. Qt 5&6 and GTK 3&4 applications run on Wayland and most don’t even need a dedicated Wayland port.
It doesn’t? Don’t get me wrong it’s great that Wayland works on so many QT and GTK applications, but if it doesn’t work on the key applications users interact with daily, then it’s kind of a moot point, isn’t it?
No, but it is a fact that Gnome is ahead in Wayland support and all major distributions (Debian, Ubuntu, Fedora, RHEL) default to Gnome with Wayland, therefore your claim of low adoption is just wrong.
Yeah you have a point, Gnome is certainly popular but is that because of Wayland or other reasons? I think Wayland support isn’t the reason why Gnome is recommended by default and I think it’s a bad idea to even recommend Gnome by default because it deviates too far from Windows design which most people would be most familiar with. A better choice would be KDE in my opinion but ofc as we have discussed KDE has its own downsides.
KDE doesn’t push anything down your throat, you’re just incapable to replace KWin with an alternative, even though at least one wlroots-based one exists.
KDE used to be able to switch out the compositor in the gui, but they removed that feature. And kwin comes with plasma by default. True I can definitively replace kwin but I don’t currently know how to and I don’t want to break plasma either.