[spudlyo]

Hard disagree. Sometimes the terminal is the most efficient way to run Emacs on a machine in a remote data center that has a mountain of CPUs, GPUs, memory, and disk. TRAMP can be slow and inefficient. A LSP server process on a huge monorepo can chew up a large amount of memory and CPU on startup. Running all of this stuff locally on the actual hardware your code needs to run on is great.

[gpderetta]

TRAMP is great, but to me it never feels the same as running locally. OTOH ssh -X (i.e. X forwarding) works for me for exactly this specific case (large and powerful remote dev box).

Incidentally my current setup is that I'm WFH and RDP'ing into my windows desktop, where I run VNC to our xvnc server where I ssh -X to the dev box where I run GUI emacs. It is surprisingly usable (I can also skip the RDP and run VNC directly if needed).

[ghosty141]

> to run Emacs on a machine in a remote data center that has a mountain of CPUs, GPUs, memory, and disk

But then why not run the daemon on that server and the GUI locally?

[spudlyo]

Have you actually tried that? I know the server _can_ expose a TCP socket but it's not clear to me if it's intended to work across machines.