Comment by pjmlp
2 years ago
No, the whole UI runs on the client machine, which in X Windows nomenclature is the server.
The client application (on X Windows nomenclature), runs on the remote server and is headless.
Instead of sending streams of bytes to render text, it sends streams of encoded X Windows commands to draw the UI.
Everything else regarding compilers, subprocesses and what have you keeps running on the server, regardless how the connection is made.
Think big X Windows terminals or green/ambar phosphor terminals accessing the single UNIX server, used by the complete university department.
I'm surprised pjmip is missing the point here. Or maybe I am
> Instead of sending streams of bytes to render text, it sends streams of encoded X Windows commands to draw the UI.
(Simplified) VSCode is sending no bytes to a server when you're editing a file. The entire file exists on the client, you can edit all you want and everything stays on the client. Only when you pick "save" is a data sent to the server.
My understanding with X Windows is as you mentioned above, you press a key, that key it sent app on another machine, that other machine sends back rendering commands. Correct? Vs VSCode, you press a key, nothing is sent remotely
Note: There's more to VSCode, while it doesn't have to send keystrokes and it is effectively editing the file locally (so fast). It does send changes asynchronously to the remote machine to run things like the Language Server Protocol stuff and asychronously sending the results back. But, you don't have to wait for that info to continue to edit.
No, you are correct. On any sort of low bandwidth or high latency connection, your remote X experience will be terrible.
Thanks for elaborating, it helped a bit and now this section of the Wikipedia article fully clicked for me:
"""The X server is typically the provider of graphics resources and keyboard/mouse events to X clients, meaning that the X server is usually running on the computer in front of a human user, while the X client applications run anywhere on the network and communicate with the user's computer to request the rendering of graphics content and receive events from input devices including keyboards and mice."""