What really frustrates me about Wayland is we're replacing an old system with lots of structural problems with a new system with lots of structural problems, and when it comes down to it X and Wayland are problemy for the same reason: They both farm out way too much core functionality to extensions, leaving a fragmented vendor ecosystem and disjointed developer experience. We got to do it all over and we made the same mistake! We don't even get to trade up to a DIFFERENT fundamental flaw!
In the current twilight moment the proposition with Wayland is Linux is giving up inbuilt GUI network streaming with the supposed benefit of a system which structurally works better on "unusual" display devices such as phones and VR helmets. However it seems unlikely we'll ever get to USE that benefit, because the hardware you're hoping to target there is hard locked in to Android— not Linux, Android. Unless you can appropriate Android GPU drivers or build Wayland atop SurfaceFlinger, who cares?
Like I think we absolutely need to make Wayland work, I've been yelling for a GPU-centric compositor in Linux since Rhapsody, but at the moment I am *disappointed*.
@mcc I switched from windows specifically because the lack of perceived control. Linux desktop attract people with weird, and unusual requirements.
@ekg At least three different commercial OS companies have built out fully adequate API stacks for this at least five different times. The open source community is doing something wrong.