Red Hat Expecting X.org to “Go into Hard Maintenance Mode Fairly Quickly”
What irritates me with regard to Wayland is the assumption that all rendering is local.   The great thing about X was on a <i>LAN</i> you could bang up an ssh session somewhere, carry across your $DISPLAY and have the exact same application running somewhere else but rendered to your screen. It doesn&#x27;t sound like much but there were times when it was incredibly useful.<p>Thin terminals brought this to the logical conclusion of not needing a desktop at all, but unfortunately X&#x27;s protocol is too chatty and sensitive to latency to really shine across a WAN.  These days you can work around all of that by opening a session via Guacamole or the like but that&#x27;s still one tab in a browser per graphical session.  There&#x27;s no just using SSH in a for loop and opening up a raft of xterms to a bunch of machines in Wayland, AFAIK.<p>From the Wayland FAQ<p><i>Is Wayland network transparent &#x2F; does it support remote rendering?</i><p><i>No, that is outside the scope of Wayland. To support remote rendering you need to define a rendering API, which is something I&#x27;ve been very careful to avoid doing. The reason Wayland is so simple and feasible at all is that I&#x27;m sidestepping this big task and pushing it to the clients. It&#x27;s an interesting challenge, a very big task and it&#x27;s hard to get right, but essentially orthogonal to what Wayland tries to achieve.</i>