Hacker News Reader

Comment by bluejekyll | Hacker News Reader

I think the use of IDEs really made this practice less simple. Terminal mode emacs and vi/m are simple with SSH, VSCode and other things start getting more complex.

I think the extensions to VSCode and others to run remotely with a browser are starting to bring some of this back into fashion.

View on HN

Connecting over SSH with VSCode is the most convenient SSH experience I've ever had: VSCode runs locally, connects via SSH and makes it feel like I'm working locally. I can edit files, open terminals, run software, etc. It's like running vim, a couple terminals and a scp file manager, but with the convenience of a desktop application

Technically you need an extension (Remote - SSH) but I think that's installed by default. It runs some remote code on the server to make it more seamless, but that has never gotten in the way.

Unless something has changed, VSCode runs in a server / client model with the FE on your local machine and the code / language servers running remotely (I don't use it, I stick to neovim).

VScode has connect to remote server via ssh mode built in, and there's an extension to use a docker container on the server, making it pretty easy to provision dev environments for new developers.

only if you are developing on a remote server which I never do.

I do use GUI text editors, file browsers and other tools that work over SSH.

some of us have the misfortune of having to use wsl…

Reply on news.ycombinator.com