3 ms·

> VS Code has one as far as I am aware uniquely-implemented feature -- remote editing -- which is absolutely invaluable to me as a freelancer with many long-ter

> VS Code has one as far as I am aware uniquely-implemented feature -- remote editing -- which is absolutely invaluable to me as a freelancer with many long-term, infrequently-updated projects. To be that one guy, Emacs has had remote editing (without even needing to install anything on the remote server, unlike vscode) for forever with tramp mode. But other, more accessible/modern editors having it is definitely nice because it's such a handy feature

bemusedthrow75 3y ago
I guess Tramp mode must be the inspiration, to some extent. But the VSC approach allows me to customise the tool environment within the remote extension, including going as far as using different SCSS processors and language servers, but is managed through essentially exactly the same interface as the local. (It's also inherently multi-user; changes are reflected in each machine connected to the remote, which makes it really easy to move from a work to a home machine, or a desktop to a coffee-shop laptop.) This is what I meant by uniquely-implemented. I often find that the most visceral critics of VSC or adherents of "natively implemented" code editors haven't the slightest awareness of this feature. Still -- thank you for your comment, it gives me one more thing to investigate for those times when tools fail me.
- flamwenco 3y ago
  Yeah, I certainly didn't mean it as a slight against VSC. (I am very much an electron hater but VSC is an exception because they obviously put in the effort to make it work as well as it does.) Much as I love Emacs I do mostly use VSC these days, and I do tend to forget the extent of what remote editing capabilities it provides since I haven't had much reason to use them in a while.
  - bemusedthrow75 3y ago
    Yes -- sorry, my comment about critics may have come across as aimed at you, but it wasn't! I was thinking more of all the other times this has come up in the past and I have to say, "you understand it's not just a text editor with network access?" It has pretty much unique capabilities, and as another commenter has said, it's even remarkably agnostic as to the _kind_ of remote container. For example you can run the editor on Windows with the remote as WSL, and it really blurs the boundaries between them in a way that cannot possibly be a coincidence for Microsoft.
bmitc 3y ago
Everyone always brings up Emacs with regards to VS Code's remoting features, but I have yet to see anything that supports that it is anywhere close to VS Code. With VS Code, I can develop across Windows, Docker, Linux, Linux running on WSL, and macOS with zero configuration aside from setting up SSH connection configs and installing the remote extensions with a button click. All the extensions work seemlessly when remoting. My settings also automatically sync by just signing into GitHub. With Devcontainers, I don't need anything to develop except Docker and VS Code. I simply pull down a repository, open it in VS Code, and then VS Code sets up a container with all dependencies and configuration. No, Emacs does not have this experience. And I don't know the technical reasons why VS Code installs on the remote server, but I think it's important to note that you're not just editing remotely but developing remotely.
- urbandw311er 3y ago
  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! :-)
  - bemusedthrow75 3y ago
    Ohh you're going to enjoy this when you get to it :-)
- tiberious726 3y ago
  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
  - deleted 3y ago
    [deleted]
- jebarker 3y ago

bemusedthrow75 3y ago

I guess Tramp mode must be the inspiration, to some extent. But the VSC approach allows me to customise the tool environment within the remote extension, including going as far as using different SCSS processors and language servers, but is managed through essentially exactly the same interface as the local. (It's also inherently multi-user; changes are reflected in each machine connected to the remote, which makes it really easy to move from a work to a home machine, or a desktop to a coffee-shop laptop.) This is what I meant by uniquely-implemented. I often find that the most visceral critics of VSC or adherents of "natively implemented" code editors haven't the slightest awareness of this feature. Still -- thank you for your comment, it gives me one more thing to investigate for those times when tools fail me.

flamwenco 3y ago
Yeah, I certainly didn't mean it as a slight against VSC. (I am very much an electron hater but VSC is an exception because they obviously put in the effort to make it work as well as it does.) Much as I love Emacs I do mostly use VSC these days, and I do tend to forget the extent of what remote editing capabilities it provides since I haven't had much reason to use them in a while.
- bemusedthrow75 3y ago
  Yes -- sorry, my comment about critics may have come across as aimed at you, but it wasn't! I was thinking more of all the other times this has come up in the past and I have to say, "you understand it's not just a text editor with network access?" It has pretty much unique capabilities, and as another commenter has said, it's even remarkably agnostic as to the _kind_ of remote container. For example you can run the editor on Windows with the remote as WSL, and it really blurs the boundaries between them in a way that cannot possibly be a coincidence for Microsoft.

bmitc 3y ago

Everyone always brings up Emacs with regards to VS Code's remoting features, but I have yet to see anything that supports that it is anywhere close to VS Code. With VS Code, I can develop across Windows, Docker, Linux, Linux running on WSL, and macOS with zero configuration aside from setting up SSH connection configs and installing the remote extensions with a button click. All the extensions work seemlessly when remoting. My settings also automatically sync by just signing into GitHub. With Devcontainers, I don't need anything to develop except Docker and VS Code. I simply pull down a repository, open it in VS Code, and then VS Code sets up a container with all dependencies and configuration. No, Emacs does not have this experience. And I don't know the technical reasons why VS Code installs on the remote server, but I think it's important to note that you're not just editing remotely but developing remotely.

urbandw311er 3y ago
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! :-)
- bemusedthrow75 3y ago
  Ohh you're going to enjoy this when you get to it :-)
tiberious726 3y ago
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
- deleted 3y ago
  [deleted]
jebarker 3y ago