> I'd agree with you if X was actually maintained, but we need to accept that it isn't. Which is a self-fulfilling prophecy as the Wayland developers were the

> I'd agree with you if X was actually maintained, but we need to accept that it isn't. Which is a self-fulfilling prophecy as the Wayland developers were the X11 developers. To be fair, I don't disagree with them. X11 was meant for a much different world. However, the Wayland developers have made some significant architectural mistakes. Fractional DPI for scaling is a clusterfsck. The memory ownership model is disastrous and makes communicating with languages other than C/C++ actively problematic. I can go on and on. Wayland, itself, needs more than a little bit of reboot at this point. Vulkan/DX12/Metal has won--Wayland should be built around those abstractions. WASM seems to be handling interop and bootstrap better and better--it should probably be based around that rather than DBus. Mouse/Touch/event/etc. management needs to be rethought and probably refactored as much as possible out of Wayland. etc. I suspect a lot of the problem is of the same origin, everybody wants to have unified abstractions for mobile/web and desktop. The Wayland/Gnome people do not want to have to write code twice--once for mobile/web and once for deksptop. In reality that turns into mobile/web abstractions for everything and desktop can go suck eggs.