Walaynd is not relevant going forward
Wayland throws out the network aware client server model.
This will make it essentially DOA as it prefers a holdover from a bygone age of RDP and VNC. Yes Wayland developers/fans, your love of RDP and VNC is, well, too funny. You want to know what is obsolete, RDP and VNC and anything that works like they do.
The client/server model needs to be EXTENDED. Sure X needs cleaning up, so does OpenSSL, so clean it up already. A replacement should replace and extend the original, not move backwards to do what toy operating systems such as windows do, with sending compressed screenshots around the network.
Plan 9 has already shown us the way, no compressed screenshots there and a simple elegant fully network agnostic process space. My ENTIRE desktop of running apps may all be remote, running on multiple separate machines, yet appear to all be local to my smartphone. So Wayland, you have the chance to implement the 9P protocol and move beyond X. Take it. But you wont, you will just let it sit and rot as everyone uses RDP and you say "well someone else can implement 9P if they really want to". Do it yourselves. If you want to replace X, actually replace it.
So RDP and VNC? surely that must be a joke? Seriously, to use a remote application/program I must launch a RDP or VNC client, enter an IP address, enter a password, then use f*cking scrollbars to navigate around a live image of a remote desktop?
Anyone who thinks that is good has no idea of what it means to use an X client over the network.
Wayland thus seems to only exist because someone cant stand the headache of debugging X, so they in their limited scope decide to chuck it away totally ignoring the main feature set that they should be extending as we all know that what Plan 9 does is the future of computing.
True cloud computing, where local and remote resources, client UI's and even processes and HARDWARE will appear all together locally in your hand or on your desk. Sure, some things will NEED to be actually local, like the flash drive you just plugged in, or the printer in the house, but your applications may not even be running on your machine, or may only be in part. Wayland with RDP totally breaks that, yet X, the old bloated beast that we know it is, does it just fine.
Just think about it. Why have a powerful GPU when you can use a remote GPU? System builders like me will love a nice GPU sure, but why cant we let a mobile phone on a train use the computing power of a remote GPU, as if it is local? No, use your laof, I dont mean that we UPLOAD a job to a remote SERVICE, then download the result, the remote GPU will be LOCAL and exist in /dev so we open it like any really local GPU.
So tell me Wayland, if you cant (dont want to) do the simple act of letting a remote program render its UI locally to me, without sending screenshots of a desktop to me, how do you think your project is relevant going forward considering what we will eb able to do with what I described above?
We don't really use the network features of X enough yet. But we will. Windows etc will have to migrate to this new paradigm to remain relevant, it will happen on mobiles and tablets first most likely. Linux, with X will just need a little shove to get going, heck Linux will be used to develop it for the mobiles anyway so the shove will probably be a tickbox on the distro installer. But with Wayland, yeah, wont happen, not without someone coming along and re-implementing a network aware GUI protocol. If we are lucky, Wayland will take it from Plan 9. If we are not, some windows gamer kid will write something that looks cool and windowsy.