If I have to deal with yet another Electron based editor, there is no reason to go beyond VSCode.

At least Microsoft knows how not to make it suck so much.

I don’t think I would be that harsh in the com plugin for vscode. It works fine for me. I’m not a vim power user though.

They are planning to use neovim as a backend for it too.

That looks really exciting actually! https://github.com/VSCodeVim/Vim/issues/1735

VSCodeVIM has neovim support too https://github.com/VSCodeVim/Vim/issues/1735. It's still an experimental feature though.

Also neovim rewrite: https://github.com/Chillee/VSCodeNeovim

How does VSCode Vim bindings compare to Vintage mode in Sublime?

I like the idea of Oni, but I also love that Sublime is native (I'm already running FF Quantum, I can't burn too much more battery!). I know Sublime's Vim keybindings aren't that complete.

I've found VSCode Vim bindings _really_ buggy. Sometimes non-responsive to the escape key until I press it a few times, sometimes it will kill highlighting of code blocks until I switch modes, sometimes enters `<tab>` in the source code instead of tab when I press the tab button. I still use it, because I've used modal editors for so long and I like everything else about VSCode, but the vim bindings are my biggest point of frustration with it.

Sublime's vintage mode is, in my experience, light years better, if not in completeness, at least in stability.

What platform are you on? I've experienced no major issues with the vscode vim plugin on Mac or Windows.

The escape key issue you mentioned was the only problem I've also had, but it's due to conflicting keybinds between the vim plugin and the vscode bindings for dismissing notifications and context help. I rebound all of those to shift-esc (and I believe the plugin's bindings now do this by default) and the problem went away.

I'll have to check out the key bindings, thanks for the tip. This is on OS X (High Sierra)

I feel your pain :)

I have been keeping Oni and VSCode open while I work so I can use Oni for editing and VSCode for the nice diffs and replace in project functionality.

How does VSCode vim plugins compared to evil-mode of emacs?

evil-mode is actually useful. VSCode's vim plugin loads really slow when you change project, doesn't have proper insert/normal/visual mode map, etc.

Have you used it recently? It works pretty well (?)

It works pretty well for movement, selection, etc. Anything that uses longer key chords is out—vscode is limited to two keystrokes afaict. It's really frustrating trying to replicate a highly customized spacemacs or vim setup.

Some time ago I used to work on VSCode with vim plugin and to tell the truth all those vim plugins were nothing compared to spacemacs or evil-mode on vanilla emacs.

the vscodevim plugin still has problems with things like scrolling (c-e, c-y, c-d, c-u) and is missing ex commands. Evil is more comprehensive

The slow scrolling key-repeat issue was recently fixed.