Re:The X-Windows Disaster (1994)
by astrodust on Thursday March 05, 2020 @07:29PM
(#22499959)
X in all of its ugly glory was and is still better than RDP.
[ Parent
| on HN ]
I'm thinking you may not have actually used RDP over a medium-to-low bandwidth or medium-to-high latency connection. Because RDP is still usable and X is a laggy mess.
Xlib, the original C binding to the protocol is not great in that situation, because it makes many asynchronous requests look synchronous. Most toolkits are pretty terrible in that situation. libxcb instead of Xlib can be a great improvement as it exposes what can be asynchronous (though it often isn't used well).
I regularly ran X over ISDN back when that was a thing. Framemaker wasn't exactly snappy, but it was usable. Lighter stuff was fine. Watching contemporary RDP keep up over 64k was painful.
With server side font rendering all but forgotten among other things, any modern app will struggle over a low bandwidth link well. And X has always been crap for latency, even with xcb, it ends up being very round-trip heavy. Modern technology has addressed the bandwidth problem, but has a much bigger challenge with the second.
Re:The X-Windows Disaster (1994)
by throwaway2048 on Friday March 06, 2020 @12:59AM
(#22501302)
Modern RDP can do seemless remote audio and full 60fps video and 3d graphics, on windows servers. Linux server stuff like libvirtd just uses it as a glorified VNC.
It blows away x11 forwarding.
https://xpra.org/ is a vastly superior solution for linux servers.