(http://www.autoadmit.com/thread.php?thread_id=3761551&forum_id=2#34427247)

really the main advantage of learning vim (aside from quickly being able to edit files in the terminal) is that vim bindings afford a de-facto standard across all IDEs with a vim plugin for basic text editing.

(http://www.autoadmit.com/thread.php?thread_id=3761551&forum_id=2#34428305)

pre-good editors I probably would've used emacs, since it's basically an all-in-one environment and extending it via macros being was one of the building blocks. vim add-ons are often clunky and slow it down/don't work.

(http://www.autoadmit.com/thread.php?thread_id=3761551&forum_id=2#34427168)

Refactoring is a HUGE one. I don't mean straight find and replace, but stuff like mass applying naming rules across your project for anything you may have typed wrong. This matters when your work enforces style suggestions as warnings

Setting up a good vimrc is a huge pain in the ass. And then you have to do it all again when you switch languages. I LOL at webdev tools who spend so much time fidgeting with vim because they (subconsciously--consciously they'll justify it with some dumb reason) want open source edgy cred. Your startup doesn't matter, everyone who isn't in a nonprofit except people doing research/toolchain development type stuff, ie not you, is a corp drone.

GDB (and I assume clang equivalent) is very competent but debuggers are just easier to use graphically. The gui really helps for organizing information here

Etc

I think a big part of vims resurgence is web 3.0 types who literally only ever write JavaScript. They're used to the SHIT debugging you get with node, don't have to set vim up for more than one language, and use the same set of functions over and over again

(http://www.autoadmit.com/thread.php?thread_id=3761551&forum_id=2#34448108)