> One solution for remote development is to handle some heavy lifting like responsive display logic locally in the client. Another example is emacs in server m

> One solution for remote development is to handle some heavy lifting like responsive display logic locally in the client. Another example is emacs in server mode: although normally folks use a Unix socket, it's possible to use a network socket instead. The remote emacs actually contains all the state, and the local emacsclient just connects to it. Another approach is to run emacs locally, and access remote files & commands with TRAMP.