I used to spend a lot of time messing with Vim configs, memorised enough shortcuts to save me time, and set them up in my dotfile repo. I have since switched to

I used to spend a lot of time messing with Vim configs, memorised enough shortcuts to save me time, and set them up in my dotfile repo. I have since switched to VS Code permanently and I would not look back. It just works with so many toolchains/workflows, and as much as I dislike electron, it is in my estimation, no less productive than my Vim-zealot setup. The command palette is good enough to navigate functionality for me. It is my personal opinion that there is no good reason to learn Vim or its variants nowadays with the current tooling available. We should be trying to innovate on something better than text editing for producing code because there has been next to _zero_ innovation (imo) in paradigms for producing code for literal decades and I know there is an opportunity for something better. I don't know what that kind of 'better' would look like but I'd be really interested to find out.