And worst of all Wayland doesn't touch yet the MOST IMPORTANT "feature" that is proper Multi-GPU support... if it ever will properly... since its an event-driven mechanism very deep hard-wired in core, since that seemed to solved better some of the issues its developers focused the most(IPC like communications).
But what is REALLY REALLY needed is a *multi-threading protocol*... because the future is Multi-GPU or Multi-Core or Multi "compute unit" GPUs, that could be addressed exactly as CPUs are today. And this even for Ultra-Mobile GPUs of the phone/tablet ARM world.
I don't know why devs keep complaining hardware changes a lot... the writing has been on the wall for some(long) time now.
At least *Shatter* tries to address this... which "a priori" makes it already better than Wayland without any further issue.
Crazy gits on windows world, have been having boxes with even 4 GPU cards, while in Linux you got to be content to have one that works well... which is not often, and not with all GPUs... and worst of all, usually things tend to break from one version to the next of the all stack, from drivers to the WS, even if you keep the same card... or more frequently if you change for another, even if it is one of the same family and vendor.
Wayland solves nothing of this.
Only a more deep and direct involvement of the vendors could... but i'm afraid Linux is being set to be the battleground for pesky politics of hardware wars...
...screw the user... who pays the piper chooses the tune... so its my way or the highway... what is important is others not to supplant me... even if it means keeping it a 3th class gaming/desktop/display environment -> The Rational