I had a couple aborted attempts to switch to neovim, https://www.lazyvim.org/ is what finally got me to switch. It has what I needed to get going, and I bookmarked the keymaps page as I got familiar.

probably not something to use in 2023

(unless you need to support old browsers)

I found lazygit because I’m on the first team in my career that encourages rebasing over merge commits, and rebasing was a PITA. Lazygit makes it so easy to rebase. Freaking fantastic TUI.

Praise be to react-hook-form for saving us all 🙏

This is exactly where I’m at. Learning vim binding has also opened me up to a lot of REALLY great TUI options. lazygit has become something I never want to work without again, and it’s only pleasant if you’re used to vim bindings. There’s also k9s and other great TUI tools out there that make learning vim bindings hugely worth it.

But, after investing a week into heavily trying to get neovim working, I went back to VS Code w/ vim plugin. Still want to get neovim working for me at some point but will have to find time to do it without hurting my professional output.

I will say so far the only pain point I’ve found running vim plugin in VS Code is missing ctrl/cmd + d… I used to use that a lot to do some really powerful multi-cursor editing and vim bindings ruins it. I actually went and disabled the vim plugin just to go do one thing with uninhibited multi-cursor a while ago, and turned it back on when I was done.