Well, it's more "Core competencies of hackers in the C/C++/UNIX/Scripting/Web tradition."

Most of the great Windows hackers I know use Visual Studio. Most of the great Java hackers use IntelliJ. Of course, people in the UNIX/web tradition would probably not admit that great hackers exist in those cultures, but they've put out some pretty impressive software...

Also - I suspect that great UNIX/web hackers don't use IDEs because the IDEs for those languages suck. I work on a C++ web team. If you glance around our monitors, everyone has the same setup: 4-6 terminals, 3-5 emacs/vim windows open, and Firefox. The funny thing is, many of us are ex-Java programmers, and we all used either IntelliJ or Eclipse in our Java programming days. And would love to use something like IntelliJ for C++, but we took one look at the C++ support in Eclipse and ran back to vim.

As a data point, I have Firefox building under Eclipse/C++ reasaonably well. I had to hack the Eclipse project files to tell it where all the headers were (arguably more a fault of the Mozilla build system), but since then it's worked surprisingly well. I'm under the impression that Eclipse's C++ support had improved substantially in the last year, although I can't say for sure, since this was the first time I'd used it.

"We haven't met a single great hacker that relied on an IDE, although we hear they exist."

Sounds like GiraffeSoft folks don't use languages with type info and a graphical debugger. I certainly wish TextMate could handle static info and had a JVM debugger. I would love to code scala in TextMate.

The IDEs are too heavy. I don't like them. But if you want/need a debugger and type info for refactoring and exploration, you don't have much choice.

The other three items they list seem on target. The one about great coders don't use IDEs is highly dependent on what language and kind of code your writing.

Without getting in to what those preferences are, that being a different can of worms, I think it's likely that there are trends in the language preferences of great hackers. The existence of these trends means that tools that work well with the languages great hackers prefer will be more popular with great hackers.

The static analysis done by heavy IDEs isn't the only way to have large amounts of information about code available in the editor. Using Emacs with Slime, the editor has a huge amount of information about your code because it's communicating with the Lisp runtime that's evaluating it.