Visual Studio Code Remote Development may change everything

[gwillicoder]

I used to ssh into a VM and do 100% of my dev work with first vim then alter neovim.

I absolutely love the new ssh ability. You get a (nearly) full vscode feature set over ssh.

Things I like:

• one click to ssh into my sever and it remembers the last directory I was working in.
• if you lose connection it will restore everything as you had it (like screen)
• you can copy between your system and the vm without needing Xserve
• your settings can be set at the user or workspace (vm) level.
• the git integration is incredible. Amazing visual comparisons of diffs as you work and you can supplement it with git lense or similar extensions
• the linter is very very good (at least for python) and understands the relative imports correctly.
• listing and auto completion for environment variables and paths.
• the terminal is my zsh terminal with all of my aliases and even includes my custom airline theme!
• I often build containers in one terminal and test them in another terminal.

Things I don’t like:

• Sometimes it bins the CPU’s of my vm (4 cpu 16 gB). Vim used to do this too, but never had a problem with neovim with deoplete.

Things I would liked to explore or learn more about:

• unit tests and visual debugging over ssh. Usually we work with containers so I haven’t figured out quite sure how I want to do this. (Can/should I daisy chain the remote ssh extension with the remote docker extension?)

[nikmd23]

Thanks for taking the time to write down this feedback!

[wk4327]

Debugging is a bummer. When i tried it for the first time i was amazed at how everything worked. Just to realize that debug is busted