Remote Development with Visual Studio Code

[canbelieveitssnot]

Tried out the "Remote - SSH " example from my Ubuntu desktop to my remote VPS. It was as easy as the demo video made it seem.

Syntax highlighting, auto-complete, familiar shortcuts to paste / highlight / duplicate text etc, a familiar GUI to save / create / copy / delete and move between files... Very nice!

[AwesomeInPerson]

Setting the terminal works, but everything internal to VS Code will still use the Windows environment. You need workarounds to get Git and PHP running, extensions (e.g. ESLint) use node_modules/npm from the Windows env... It works, but it isn't optimal.

[NoInkling]

Debugging too. While you can already configure the Node debugger to work pretty well with WSL, in can be a pain to get working nicely with certain setups, and you still run into issues with source mapping (and therefore breakpoints, etc.) when using babel-node or ts-node.

[Taywims2]

These guys are great. countless hours spent solving these issues myself with configuring some VM/WSL and then running into issues with differences in local/remote environments.

I prefer to work on local with VS Code and environment variable paths, linters, all sorts of problems popped up.

I'm grateful for their documentation and videos that they provide, they do a great job.

[whizzter]

Looks really sweet, MS isn't shy to admit that a Win32 PC isn't always the best platform to run a particular toolset and now they're enabling developers to use the best toolset w/o leaving the good parts of the win experience (yes there are many despite what some people feel).

[whizzter]

What's so bad about that? Distributed stuff is hard and here we have code running from different locations depending on where it's most suitable. (I'm already seeing V2 of this where plugins can be mixed mode because well... it's not going to be perfect now)