4 ms·
Personally I like Vim because I do a lot of coding while in an SSH session and it's easy to port my setup very quickly. My work involves using a workstation wit
by andreyk 4y ago
Personally I like Vim because I do a lot of coding while in an SSH session and it's easy to port my setup very quickly. My work involves using a workstation with a GPU so I am not able to do that at home, and debugging requires me to run things from command line a lot to know what to change in the code. No doubt I could create a set up with a fancier IDE to do that, but at the scale I'm working in (academic code with just 1000s of lines of code) there is really no need.
- jdrek1 4y agoYou could also use VS Code's remote (over SSH) ability.
- ftufek 4y agoYou can do the same with vscode btw. I also work on remote gpu workstations and vscode remote with ssh works just fine, especially if you use tmux, you can preserve all the history and what you were doing.
- RMPR 4y agoIn my experience, vscode remote code editing is very buggy and resource hungry. Not very fitting if your Internet is unstable/slow and/or your target workstation is not that powerful (why is 8GB of RAM not enough?). I've had more success with Neovim either with distant.nvim[0] or directly on the Workstation with mosh[1] 0: https://distant.rocks/ https://distant.rocks/ 1: https://mosh.org/ https://mosh.org/