That's like saying the phone has overtaken the horse.
I doubt many people sshing into a box using vim will choose visual code. There might have been some people using vim for daily development who switched but probably not many
vscode actually is very convenient when working on remote machines. You'll run the vscode editor on your own box, but have it access the remote's filesystem over ssh.
https://code.visualstudio.com/docs/remote/ssh
Probably overkill for occasional remote file editing (it'll run some server component on the remote machine), but pretty good for more involving remote development work.
> I doubt many people sshing into a box using vim will choose visual code.
Actually I do just that.
With the remote development tools I can open a remote folder in vscode and edit from there. And when I start terminals, they're going to start a shell on the remote linux box.
I have once .vimrc configured for all the languages that I use/know.
Whenever I work with a new client. I pull that .vimrc on the allocated machine. Run PluginInstall and in minutes I am ready to go!
I would claim the opposite — VSCode is nearly unusable without very heavy customization unless you're fine with being very inefficient. Hotkeys for many common operations are not assigned out of the box. Without that, using it involves driving the interface with both the mouse and the keyboard. Those that are assigned are awkward and look like they've been designed for a spider since they require you to reach keys on the opposite sides of the keyboard. I always get the feeling that its own authors don't use it for anything more complicated than editing /etc/hosts, although it's quite obviously not true.
I remember when Emacs was viewed as requiring a lot of resources (in the early 1990s) and I remember the sysadmin of our shared UNIX system scolding us if we had more than one emacs process running (as opposed to opening multiple files in different buffers).
I've been using VSCode kinda on and off, but I haven't learned it properly yet. Do you think it's truly worth it? It seems to me like you'd use it mainly when you don't have access to a full IDE, so I haven't really found a niche yet.
I wish someone could show me actual repl work in vscode for a lisp or erlang. It sometimes gets the way there, but doesn't to make it.
I think the plugin writers are either shoe-horned by VCCodes lack of plugin capability or they are basing their work off some other toolings expected behavior and it doesn't "sit right" with how I work.
I doubt many people sshing into a box using vim will choose visual code. There might have been some people using vim for daily development who switched but probably not many