Moving past a text editor is a big help.
Only if you consider a text editor and commandline tools to be a throwback to previous decades. They haven't stood still, you know...
Refactoring support matters
Euch: sure it would be nice, but last time I checked the status of C++ refactoring tools, they were far too buggy to be reliable. Things may have changed since then. Also, the refactoring tools tend not to work on half of the languages I use regularly...
Code completion (intellsense, etc) support matters too.
Editors have this now too. You can run it in vim variants. Personally I only like it a bit when I used it. I find I ended up coding to make intellisense happy (top to bottom) rather than than the way I preferred. When I went back to using an editor, I didn't go and enable it.
I find intellisense works nicely for massive and not awfully well designed APIs better than it works for algorithmic coding where you're using much fewer primitives.
Anyway that's besides the point: you can use it in editors too.
Add in things like smart templates, etc.
I don't know what they are, but the first link on google was for a text editor.
I've used IDEs and I've used the unix environment for programming. I know about all those things, but I still prefer text editors. Part of it is that they work on a lot of different systems, where as IDEs tend to be limited in scope (in practice). I've never seen an IDE that has good support for Octave/Matlab, shell, awk, C++, GNUplot at the same time for example.
They also have weird-ass build systems on the whole that do things in a much more complicated way but with no extra utility compared to GNU Make for example.
Integrated debuggers are nice---for certain kinds of code. By chance I happen to often work on the sort of code where printf debugging shines.
I also hate it when other people use IDEs because frankly most people who "know" IDEs don't and do stuff like check in projects with absoloute paths, so they fail to compile anywhere except the original user's machine etc.