[mraison]

Very happy about this move. Nuclide’s remote development capabilities were way above anything else I’ve tried (Sublime, IntelliJ Ultimate, VSCode, remote SSH mounts, etc).

It’s the only solution I’ve found that really allows you to browse the remote filesystem as smoothly as you would with your local drive (including when you’re also changing the remote files outside the IDE), degrade functionality as needed when the connection isn’t great (using caching appropriately), and immediately recover when it comes back. The only cost to pay was a bit of setup server-side (installing watchman and opening a port, if I remember correctly). I really hope they can bring the VSCode experience to the same level!

[shaklee3]

What is missing from vscode for remote development? MS released their remote development extensions earlier this year, and everything from browsing to searching feels native.

[lioeters]

I haven't personally tried it yet, but the positive reviews made me curious - I'll have to check it out!

For reference, here's the documentation page for VS Code Remote Development:

https://code.visualstudio.com/docs/remote/remote-overview

The Remote Development Extension Pack (linked in the article):

https://marketplace.visualstudio.com/items?itemName=ms-vscod...

[mkohlmyr]

Do you happen to know if it works for vagrant VM's? Because having a file system mismatch (symlinked dependencies in vm, IDE doesn't recognise them) is a bit of a pain point for me right now, it would be really fantastic to find a solution within VSC.

[shaklee3]

Not sure, but it works by storing files on the remote server under ~/.vscode, and this is where all the normal code files are stored. When you connect to a remote system it loads these files over ssh.

[drspacemonkey]

I've been using a Vagrant VM and VSC remote via SSH for the last two months, and it works really, really well.

[hamandcheese]

If you can SSH to your vagrant VM, then yes!

[mkohlmyr]

Looks pretty promising actually :)

[chrisweekly]

Yeah, same rxn. I tried vsc's remote dev stuff to try pair-programming w a friend in another state, and was surprised and delighted at how well it worked. It was effortless and frictionless.

[Trimbell]

I've had a similar experience. Nothing but good things to say about it, the extension works incredibly well.

[wolco]

Really? I'll give it a try. When vscode was first released this was the one feature missing.

[shaklee3]

I tried it on the first day it was released and haven't looked back. It's made me significantly more productive than with the old ssh plug-ins.

[activitus]

+1 for VSCode.... I'm still waiting for the catch.

[woadwarrior01]

Indeed, I remember trying to switch to IntelliJ locally (with SSHfs on the server), a couple of times and always going back to Nuclide because of the lag with sshfs, whilst working there. Nuclide had a lot of problems, but good support for remote dev wasn’t one of them.

[nuclear_eclipse]

From what I've used internally, the remote development bits are already better than they were under Nuclide. Adding and managing multiple remote repos/working copies is a breeze.

[thrwer34324]

Dired/Emacs has already had everything you're talking about for a long long time. There is even support for remote "inferior shells" in Emacs - notably for python.