←back to thread

Making TRAMP faster

(coredumped.dev)
226 points celeritascelery | 3 comments | 23 Jun 25 14:46 UTC | HN request time: 0.956s | source
Show context
nurumaik ◴[23 Jun 25 18:48 UTC] No.44358802[source]▶
Making tramp go brr by removing half of features

Sad to see it's still so far from vscode. Is there really no way to make emacs magically work like vscode without modifying packages

Idk maybe invent something like jit-compilation but for remote/local code. Profile rtt latency then somehow dynamically calculate optimal local-remote code split and transfer remote part to remote machine

replies(1): >>44359136 #
1. ParetoOptimal ◴[23 Jun 25 19:23 UTC] No.44359136[source]▶
There is inherent limitation of latency/responsiveness in the tramp model versus the copy vscode server to my server and communicate with it model.

The tramp model does have the advantage of little to no resource usage, but these days most aren't concerned about that.

replies(1): >>44361188 #
2. lmz ◴[23 Jun 25 23:15 UTC] No.44361188[source]▶
Indeed in many cases now the server has more resources than the client accessing it (the "thin client + remote dev box" model)
replies(1): >>44361499 #
3. ◴[24 Jun 25 00:05 UTC] No.44361499[source]▶