Well, it has to have something beyond price if it's taking by storm the editor arena that always has had great editors.
I think it has gained its place in the eternal emacs vs vim discussion, and that's a feat to be reckoned. In 15 years there will be other fancier editors but VS Code will still be there.
VS Code is good, but not THAT good. It has unparalleled remote editing with the SSH extension, but the actual editor is beaten by Sublime.
I can buy that people like it, I don’t dislike it, but it also isn’t sliced bread. There’s peers in the market that are ahead in various ways, so VS Code isn’t the end all be all, even if it is cool.
As a vim user with only superficial emacs experience, does emacs have something like the remote file system setup that VS Code with the ssh extension provides? Basically local editor with local response time, but file system is external?
I realize sshfs provides something similar, but it has a few rough edges compared to the vs code implementation.
I hesitate to dive into comparing editors, but here goes. I've used editors for a very long time, I believe the first was TECO sometime in the 1970s at the time I stopped punching cards. My preferred editors now are Emacs, Neovim, Jet Brains IDEs, and VSCode (in that order). All of them are really great professional grade tools.
Emacs supports editing remote files via ssh, ftp, or scp; one simply refers to filenames like: /ssh:host:filename or /ssh:user@host:filename. It's pretty simple and transparent. One can browse remote directories, etc.
Likewise editing a local file under a different user id is also supported using paths that look like /sudo::filename.
See section 18.5 Remote Files in the Emacs user manual[1].
Yes, when you're editing a remote file, using commands to access a shell or browse directories will open a shell in the remote system/browse remote directories- it all feels the same as working with local files.
Something I have yet to try is using an lsp server with a remote project. I'm not sure how some, like the rust lsp, that need the whole project (at least w/ emacs it doesn't yet support isolated files), would work.
I think it has gained its place in the eternal emacs vs vim discussion, and that's a feat to be reckoned. In 15 years there will be other fancier editors but VS Code will still be there.