Comment by dpassens
2 years ago
The point still stands, though. You need a roundtrip, even if it starts from the X server rather than the X client.
2 years ago
The point still stands, though. You need a roundtrip, even if it starts from the X server rather than the X client.
You always need some level of round trip between keyboard and UNIX procecess.
The server application isn't guessing keys, regardless of the connection format.
What matters is how the communication is being compressed and local optimizations.
The difference here is that VisualStudio code fully runs the GUI on the local machine and only file IO or external programs (compiler, the actual program being devleoped, ...) run remotely. Thus the UI reacts promptly to all interactions and many of the remote interactions happen asynchronously, thus even saving a file will not block further actions.
Whereas any non trivial X application does work in the client, thus even basic interactions have a notable delay, depending on connection.
You're assuming someone would be running Emacs on the remote machine talking to a local X server in order to edit files on a remote machine, but people would generally not do that, but use something like TRAMP, where Emacs would be running on your local machine, but accessing remote files.
TRAMP only requires ssh or telnet (or scp, rsync, any number of other methods) on the remote machine.
It shows you never used slow telnet sessions over modems.
There is no difference between doing this over text or graphics, in terms of the whole setup regarding network communications for data input and output.
9 replies →