The poor technicians having to RDP with (what I imagine must be) a horrible latency. Although still might be better than some corporate environments lol
The poor technicians having to RDP with (what I imagine must be) a horrible latency.
Once or twice a month, I have to RDP (now "Microsoft Windows App!") into a Windows XP machine on the other side of the continent through a jump box and a dialup connection.
Latency is bad, but not as terrible as you might think. The worst part is moving files between localhost and remote.
RDP in the windows XP days supported all kinds of tricks to work with low bandwidths like doing rendering on the client not the server.
I think most of those tricks have been disabled in modern windows for better security (you don't want some guest user able to feed your not-so-robust awfully complex rendering code some malicious inputs...)
Low bandwidth is a bigger problem than high latency. If it takes half a second or even a second for your clicks to register it's not a big deal, you learn to work around it. But if the bandwidth is so low that it takes 5-10 seconds just to write the screen it really sucks.
I don’t know if this craft has it, but they’ve been announcing all over that we’ll get 4K over a 260mbps link from the moon, so that shouldn’t be a problem
Yup. 57kbps transatlantic modem connection to a remote desktop in some country with poor telephone connectivity was probably even worse. Never want to have to do that again!
