In my opinion, turning vim (or any editor for that matter) into and async ide was not a good idea. Because random latency requires attention and kills both spee

In my opinion, turning vim (or any editor for that matter) into and async ide was not a good idea. Because random latency requires attention and kills both speed and attention elsewhere. I don’t know why exactly Bram resisted it, but I like to think he understood editing better than most. Nvim was the apotheosis of that conflict. I tried ale (set it up to get out of my way) but had frequent stability issues with it, so it stays disabled unless really needed. Apart from that, vscode is already significantly better than any options we had back in the day. It could be worth to learn vim for the sake of it, but my opinion is you’re really better off learning vscode ~programming to gain efficiency. Because all we really do to edit fast is programming an editor and calling its functions with shortcuts. Vim just happens to have a large stdlib for that. I wish I didn’t know vim. That would prohibit the comfy low-energy state and motivate me to break programming walls and learning curves that advanced vscode unfortunately has.