Thank you. Programming is not an IO-bound problem, and if it is, you're not doing anything interesting.
vim gives you ergonomic benefits? Sure, I can believe that. Allows you to manipulate text faster? Ok. But, at least in my reality, text manipulation is a rounding error when it comes to productivity. I simply do not buy the argument that using vim improves your code, or the speed at which you can write it.
I actually do find that text manipulation can become the bottleneck in the right environment, at some points in a coding session. Vim won't make you faster while staring at a pair of empty braces thinking about the right algorithm. Vim can make you faster while rewriting a function, moving code around, or typing code that you've already thought through. And I often find that the faster I can get a thought out and stop holding as much state in my head, the faster the next idea comes.
vim gives you ergonomic benefits? Sure, I can believe that. Allows you to manipulate text faster? Ok. But, at least in my reality, text manipulation is a rounding error when it comes to productivity. I simply do not buy the argument that using vim improves your code, or the speed at which you can write it.