[ipaddr]

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

[pthr]

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.

[viraptor]

Switched from vim to vscode with vimmode for the key bindings. Od definitely include it on the list for the extensibility and features.

[znpy]

> 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.

Everything via ssh.

[darthrupert]

It's like saying that the electric car engine has overtaken the oil-based car engine.

[nnoitra]

Really? Did you miss the part where both of them are editors?

[ipaddr]

Are you opening visual code in your putty session to edit a config variable? They are as similiar as word and pico.

[nnoitra]

No, but that's for basic text editing only. Anything more serious and you spending 2 hours per 6 hour development time configuring vim.

[Vijayvithal]

You configure Vim Daily? For every Task? Wow!

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!

[5e92cb50239222b]

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.