This is fun and all, but if you lose your connection, your windows will go away and your program will usually exit.

It’s almost always more usable to run a desktop session in Xvnc on the server and connect to it with a VNC client, because if you get disconnected, you can just reconnect.

Sure, although originally you'd have an X Terminal (an actual dedicated terminal device running an X server, of varying levels of performance), rather than an X server program running on your computer (i.e. an X Terminal emulator).

The terminology is of course a bit counter-intuitive, since it's program-centric rather than computer-centric - the local terminal is the server and the remote computer (or rather program) is the client, utilizing the server as a display device.

It's a bit like a text terminal (VT-100 etc) except of course the X terminal has a network connection., With the VT-100 if you wanted to connect to a remote system you'd have to use a modem (acoustic coupler) to dial into a terminal server on the remote system. I don't think anyone ever made a text terminal with built-in telnet and ethernet.

I used to do this with Virtual Box running locally. I found the performance of the windows x client was superior to trying to use x directly in the virtual machine. I wish the protocol supported audio.

Hacker's Delight is also the title of a handy reference for numeric algorithm recipes.

https://en.wikipedia.org/wiki/Hacker%27s_Delight

This is how I run graphical Emacs in WSL. And how I was developing SDL games as well.

I hear this might become a native built-in feature in Windows but for now I just run an X client.

Meh we used to have to install oracle databases this way, and the performance was always shit even over direct connections w/cross cables.

I don’t think x over ssh is useful for much, can you imagine a browser this way?

Back in about 1994, there was a server at I think MIT that would stream a live TV signal to your X Window server.

Yeah, with no compression, that's right.