In some ways, Vim programmers are stuck in a local maxima of efficiency - we're really efficient at doing edits like "search for and change this word" and "change parens to square brackets" - but if you look at the sort of advanced features that other editors have, you find that they don't care about those edits, and have chosen to automate different tasks:
Example 1: TextMate users create bundles that drop in common boilerplate easily, and they have a really nice ways to jump between files in a large project. Vim users mostly don't do either of those.
Example 2: IDE programmers tend to have syntax-aware tools that implement common tasks like "extract local variable" or "jump to implementation". Vim versions of these tend to be crude approximations that use regexps instead of actually parsing files.
Personally, the cost of typing more slowly and having to use a mouse to edit text means that I haven't ever learned to use modern editors effectively - so I'm faster as an expert in Vim than I am as a novice in Eclipse or TextMate or IntelliJ or Sublime - but in many situations an Eclipse expert is probably faster than me.
It takes more effort in vim, but for each example you've mentioned some vim user somewhere stopped and thought, "That's useful I wish I had that AND had it in vim."
Picking up Android development is the first thing that really made me consider switching out of vim. With eclim, I'm now half in half out. I do most of the actual coding in vim with eclim doing the menial work of basic error checking, automated imports, automated refactoring, etc. For debugging, and some of the layout tools I'll switch to the Eclipse instance that's already backing eclim and do it there. It's a nice compromise.
Example 1: TextMate users create bundles that drop in common boilerplate easily, and they have a really nice ways to jump between files in a large project. Vim users mostly don't do either of those.
Example 2: IDE programmers tend to have syntax-aware tools that implement common tasks like "extract local variable" or "jump to implementation". Vim versions of these tend to be crude approximations that use regexps instead of actually parsing files.
Personally, the cost of typing more slowly and having to use a mouse to edit text means that I haven't ever learned to use modern editors effectively - so I'm faster as an expert in Vim than I am as a novice in Eclipse or TextMate or IntelliJ or Sublime - but in many situations an Eclipse expert is probably faster than me.