"Mostly" is correct, but some of the problems with Wayland are fundamental and will never be fixed. From "Major Linux Problems on the Desktop, 2020 edition"[0]:<p><pre><code> - Applications (or GUI toolkits) must implement their own font antialiasing - there's no API for setting system-wide font rendering. Most sane and advanced windowing systems work exactly this way - Windows, Android, Mac OS X. In Wayland all clients (read applications) are totally independent.
- Applications (or GUI toolkits) must implement their own DPI scaling.
The above issues are actually the result of not having one unified graphical toolkit/API (and Wayland developers will not implement it). Alas, no one is currently working towards making existing toolkits share one common configuration for setting font antialiasing, DPI scaling and windows shadowing. At least in theory these issues can be easily solved, in practice we already have three independent toolkits for Wayland (GTK3/Qt5/Enlightenment).
- Wayland works through rasterization of pixels which brings about two very bad critical problems which will never be solved:
Firstly, forget about performance/bandwidth efficient RDP protocol (it's already implemented but it works by sending the updates of large chunks of the screen, i.e. a lot like old highly inefficient VNC), forget about OpenGL pass-through, forget about raw compressed video pass-through. In case you're interested all these features work in Microsoft's RDP.
Secondly, forget about proper output rotation/scaling/ratio change.
</code></pre>
[0]:<a href="https://itvision.altervista.org/why.linux.is.not.ready.for.the.desktop.current.html" rel="nofollow">https://itvision.altervista.org/why.linux.is.not.ready.for.t...</a>