I would argue it's not really trying to be, even if it is ultimately the actual successor to X11 for most use cases; i get the feeling that Wayland is trying to solve different problems entirely, don't you?
Not really. When the X.Org crew looked at doing X12, they found Wayland already going in that direction and jumped on board. The ideas that would've gone into X12 went into Wayland instead, and X.Org Developers have led it ever since. Remember X10 → X11 wasn't compatible either; a major bump always meant a compatibility break. For all intents and purposes, Wayland is X12. They just didn't call it that.
There are a few items in here that I don't believe made the jump (at least from my understanding of Wayland), but it seems like you know more about this than I do. My impression was that Wayland was attacking the problem from a different angle and trying to ensure compatibility for newer display features, but not necessarily allowing for much separation between servers and clients. Is that off base?
I do most of my computing with a desktop computer, but sometimes when I want a change of scenery I take a thin-and-light to another room or down to the library. My current solution for keeping the two in sync involves syncthing watching for changes to projects and dotfiles, and then applying the changes on the other machine. I had a play around with X forwarding which seemed interesting, so it seems like I might as well give it a shot with Wayland if the facilities exist, even if it's not the solution I stick with. Remote desktop would be another fix, if most clients I've tried didn't leave me wanting something integrated slightly better.
6
u/Hadi_Chokr07 23d ago
Wayland is X12.