- Can't work without an integrated debugger (i.e. can't diagnose a core, doesn't know how to attach a gdb to a running process, etc...)
- Can't diagnose problems outside of the development sandbox.
- Will demand access to expensive debugging tools instead of throwing some logging in.
- Doesn't code experimentally. Won't try things. Will ship the first version that works.
- Can't generate a simple test case for a bug, instead hammering away on a giant 200-file project someone else wrote.
- Often can't write a single-file, simple program from scratch AT ALL.
The analogy to a crutch is very apt. Yes, you can do great work with IDEs, and I'm sure people do. But 90% of the time an IDE user is using it only because it's all they know, and they're too lazy or unskilled to learn something different.
A real programmer uses a pen.
A good programmer can put together a system with nothing but a stack of note cards, a pencil and a good eraser.
Since good programmers can work in really archaic and restrictive environments should they? Of course not! You should give them the best tools for the job, they will work quicker. However, that doesn't mean they can't be amazingly productive with primitive tools (see the 1970s for instance).