Re: Weyland will be the future when ...
IIRC the reasons for Wayland were to get the network out of the way so it would be fast and light and to drop a pile of legacy code.
Disks are cheap and no-one is going to notice a few megabytes of old libraries that never get paged into RAM. They will notice their absence when old applications stop working. Wayland needs (has?) a compatibility library so cutting out the legacy code is a non-starter.
The old requirements of X were 4MB RAM and 12MB of swap. Yes megabytes. X is small and light. Its the applications that can be huge and inefficient. Swapping in Wayland for X is not going to fix bloated applications.
If the client and server are the same machine, X uses shared memory for 'networking', so no overhead. When the client and server are on different machines, X can run well over networking kit from the 80s by sending a command stream. Wayland draws a picture, compresses it, sends that over the network, and decompresses it on the far side (they got this working in August of last year!). Calling that a huge step backwards is over generous.
When Weyland has been stable for years, working over a network (around 50% of my use case) on kit that runs on batteries then it will be a competitor for Xorg and might actually have a future. I expect the sun will become a red giant first.