Ah right.

(Embarrassed cough)

So, er, I didn’t need to install MacOS Fuse, mount an SSH-FS folder and then use VS Code to open my remote code for editing then?

Thanks for sharing. At least I’ll know next time! :-)

Ohh you're going to enjoy this when you get to it :-)

To also be that one guy, emacs has had this with the ssh method in TRAMP basically since ssh existed. (Not the devcontainer stuff, it has something similar, but it wasn't till LXC/Docker got popular that emacs could do it that way. At least on Linux) I agree, it's amazing and great that more people are finally using this methodology, but certainly not new to VSCode

No one said it is new. It's that the experience isn't replicated by anything else, including Emacs, unless someone has a video demonstrating it that doesn't including hours of setup and years of experience with Emacs and is as seamless as it is in VS Code and gets the same ongoing support.

> it's amazing and great that more people are finally using this methodology

Okay. (Emphasis mine.)

We get it. Emacs is awesome and has been around a while. But not everybody started with it when there were no other competing tools, but now there are competing tools.

Even if emacs can handle the remote editing side I doubt the remote debugging experience comes close to what vscode can offer with very little effort.

I do all my development on remote supercomputers and the ability to remotely debug multi-process Python and C++ applications running inside containers across many servers made me love vscode.

Personally zero configuration is not a selling point for me for a professional tool I rely on to do maybe the majority of my work.

I think it’s reasonable to not hold hours or even days of setup and learning against a product I’d use in this fashion. Even a tiny 1% productivity benefit obtained after configuration and learning earns me about 2.5 dev days worth of benefit every year. And if I expect to use the tool for a decade that’s almost a month.

Why does something require setup or configuration if it just works though? How is that not a selling point? Requiring hacking to get some, now standard behavior, is not a virtue. VS Code can be configured via settings for both VS Code itself and extensions and can be extended all you want via custom extensions. It's not like VS Code doesn't support extension. It supports it rather heavily. It just comes with a huge amount of stuff out of the box that doesn't require years of hacking a .emacs file.

I don't want to install a new tool and be told I need to dump hours and days into it when another dev tool just does it where I can get on with doing what I want to do. This is exactly why I went to VS Code from Emacs.