I routinely use modern X applications running on a remote (25 miles) machine, all day long as part of my job.
It works flawlessly if you have a reasonable amount of bandwidth and reasonable latency.
Sure, it doesn’t work over dial-up.
It works flawlessly if you have a reasonable amount of bandwidth and reasonable latency.
Sure, it doesn’t work over dial-up.
That's the point, X's claimed advantages here long since stopped existing, and nobody noticed because the "inferior" approach is perfectly fine with modern internet connectivity.
It's also rather complicated to set-up on the server side (xauth, magic cookie, etc).
waypipe, on the other hand, was a breeze to use, even though it's very young. I tried with Firefox and 500Mbps of upload capacity, it worked fine as long as the window wasn't too large.
you mean "ssh -Y user@host..."?
- X forwarding over SSH: this only requires changing X11Forwarding in OpenSSH sshd's config
- Plain X over network, which is secured with `xhost`, insecure, and needs transfering the magic cookie or other authentication information
So, not nearly as complex to setup as I recalled, though it's much simpler to run a nested wayland compositor (which waypipe does) than a X11 server (which xpra does). The difference between X11 and Wayland remote access thins when xpra is involved.
https://stackoverflow.com/questions/37157097/how-does-x11-au...
That should have been 500 kbps