I'm not a VIM expert, but I do use it as my primary editor. Visual Studio Code is my secondary editor and I flip between them, but tend to be in vim most often

I'm not a VIM expert, but I do use it as my primary editor. Visual Studio Code is my secondary editor and I flip between them, but tend to be in vim most often. I don't think that the utility of VIM comes from squeezing out wpm, but in it's navigational and editing capabilities. Particularly when paired with a relevant language server, code navigation is a breeze. Additionally, being able to run it on a remote server, in a tmux session, means I can drop off and pick up my work from basically any machine without any effort. My vim config is pretty barebones, its primarily just language server support and git fugitive. Now, modern vscode setup with a remote plugin, language plugin (and vim keybinding plugin) gets you basically the same benefits. For me personally though, I find a few things more clunky in that setup than the vim version of it, mostly around code navigation.