Wayland doesn't fractionally scale chrome, discord, vscode, spotify, beeper, and other appimage and non-native applications. So even if KDE enables it by default, most users will have to switch back to X.
It doesn't scale the rest, because those are electron apps that either ship with old electron version, or disable wayland. Special mention goes to vscode, which ignores *-flags.conf and provides no other way to enable wayland, except for command line argument.
So basically it is maintainers of these apps dragging their feet.
Wayland not working with NVIDIA is a massive deal-breaker.
I've used Linux desktops on and off for the past 20 years, and it's incredibly frustrating how everything is perpetually in a state of semi-brokenness as they move on to the Next Thing. I still think about the early years of KDE4, which were a horrible regression from the stable and usable KDE3.
>Wayland not working with NVIDIA is a massive deal-breaker.
To state the obvious, though: only if you use Nvidia. And honestly, the Linux community not going out of their way to support an uncooperative hardware vendor is a good thing for everyone who doesn't use that vendor; it reduces scope.
Agreed on the frustration of chronic semi-brokenness though.
I agree; this was a complete deal breaker for me. I had no choice but to ditch Nvidia as a result. It's been really great since then. Especially not having to deal with their shenanigans when I want to do something simple like update my kernel.
FTFY: GNOME Shell/Mutter and wlroots don't fractionally scale chrome, discord, vscode, spotify, beeper and other Xwayland applications.
KDE Plasma Wayland by default applies Xwayland fractional scaling for X11 apps, which while less good than Wayland-native scaling mostly works. (If it's broken for you/an app you use, you can toggle it to let the DE scale up from 100%.)
