[prodigal_erik]

I did yet another quick search for "wayland remoting" and there still does not appear to be a well-supported story, so for me it's not even worth trying yet. In the age of IaaS and containers, who has just one computer?

[aidenn0]

It seems to me that something like xpra should be fairly easy to port to wayland. (For those who don't know, xpra installs itself as a compositing window manager, and then can render each window either locally or remotely).

[prodigal_erik]

A lot of people say "remoting wayland should be straightforward" but it keeps not happening. Either it's actually hard, or nobody on the project cares, which makes me question their judgment. Imagine how a display system would be received if it didn't support color on day one.

[aidenn0]

I think part of it is that the remoting situation on X is so bad that a lot of linux users just avoid it in favor of something like tmux or screen for remote work.

Remote desktop from the mid XP era just blows away anything that X has up to now.

[m_mueller]

What's so bad about it? I sometimes do "ssh -Y" from OSX to use some GUI tools on a server and it works pretty much to my expectations.

[aidenn0]

ssh -Y will work find on a LAN, but higher latency links are a really bad experience; X11 is a very chatty protocol with a lot of round-trip delays. On top of that, you cannot detach from such sessions. If e.g. your ssh connection gets reset, you lose any unsaved work in the program.

Traditional VNC servers allow detachable sessions, but the local use is kind of crummy.

Tools like x11vnc are closer, but they lack options to lock the display on the local machine, which is something remote desktop has done by default since at least windows 2000.

[m_mueller]

Yes, I can see that. It certainly isn't ideal and I wouldn't do something crazy like running a web service based on this technology. However at least within a LAN it's good enough and I wouldn't want to loose this capability for the sake of 'moving with the times' (wayland).