vim-awesome VS Vim

I encourage you to add plugins to your vim (tip: use vim-plug). Use vimawesome.com for inspiration.

I don't have a solution for each one of your points, but I'm going to point out a couple that are very useful for me at least (most of these can be found on a site like vimawesome or just native configuration/usage).

Vim Awesome. This is probs the best resource for text editor related plugins for vim. Browse around the site and see what looks like it would work for you. Fugitive, NerdTree, Syntastic, and surround are pretty great for utility.

Get inspired and find your new plugins at https://vimawesome.com/

I originally landed on https://neovimcraft.com because of https://vimawesome.com

then linked to a very useful guide and repository of plugins

Vim is infinitely customizable. While Vscode allows you to change the app’s color scheme, install plugins, and change a few app settings, Vim offers you complete control over the editor’s experience. You have thousands of plugins to choose from. You can completely remap any keybinding and create new shortcuts for tasks in your daily workflow. And giving you more power as a developer, you can completely reprogram or automate your Vim experience with the built-in Vimscript language or Lua for Neovim.

I find the Vim extension for VS Code has macro support that is good enough for most of my use cases (if you’re a fan of Vim key bindings - obviously).

https://github.com/VSCodeVim/Vim/blob/master/ROADMAP.md#repe...

that's why I just use https://github.com/VSCodeVim/Vim if I have to use VSCode

They have discussions enabled on the GitHub repository; eventually r/vscode might be of help.

What you would learn from using a neovim addon for VS Code covers most of the first point and some of the second - VSCode Vim lets you run neovim in a headless mode that relays keypresses to it, and emulates several popular addons. It also comes without quite as much hassle as comes from the second step of learning to configure vim/neovim yourself. Most VSCode extensions work pretty well out of the box, maybe requiring you to add the path to a compiler/interpreter that is not on your PATH.

The extension does have visualedit. You can check the list of supported features here: https://github.com/VSCodeVim/Vim/blob/HEAD/ROADMAP.md

I though VSCode's vim emulation had issues with code folding

Either I go with K552 or save for RK84 if not CB-GK-16 and both of these are pretty good choice that's certain, or I go with 617 Fizz and use VIM keybinding which Isn't an issue for me cause I've been using NeoVim for more than 1 year, you can grab my dotfiles if you want. Most people won't go with 60% cause they are used to arrow, home, end ... keys so am I with vs code but today I found out about vscodevim extension which enables vim keybinding , these keybindings pretty easy to use more than arrow, home, end .. keys if yo're a vim user like Shift + $ = end, Shift + 0 = home, in visual mode V to select text etc ...