←back to thread

Making TRAMP faster

(coredumped.dev)
226 points celeritascelery | 2 comments | | HN request time: 0.398s | source
Show context
shwouchk ◴[] No.44357887[source]
tramp is great. all the other mentioned solutions are nowhere near as seamless for “just do what i want, without distractions”.

vscode? “trust me bro, i will run a networked daemon on your server”. enjoy wondering which plugins to reinstall on your remote. enjoy installing proprietary shareware+telemetry plugins just to use git. try opening a local file and a remote file side by side in the same window. wifi connection broke for a sec? oops, you have to refresh the whole browser window.

want to edit a single file on a host you rarely connect to? enjoy spending 10 minutes setting up autosync solutions.

with any of the above - oops, you actually need sudo for that file in /etc? yeah, drop to shell and edit in vim.

there are other options to do stuff and for very specific predefined workflows they may win, but the versatility of tramp is still unmatched, especially if you do use emacs.

the only times ive had issues is when i have a weird shell setup on the remote - for that there is /sshx: instead of /ssh:

replies(2): >>44359279 #>>44366365 #
1. warsheep ◴[] No.44366365[source]
Not sure how you can compare vscode with TRAMP. A lot of dev work nowdays is done in containers where you install specific versions of dev tools, compilers, etc. Vscode is one click from seamlessly working inside such a container with its dev tools. TRAMP doesn't provide anything like that, right?
replies(1): >>44367593 #
2. G3rn0ti ◴[] No.44367593[source]
Of course, you can use TRAMP to edit files inside docker containers. You don’t even need to install anything inside them.