>>15
Can you tell your ide to run 452 tests on each nested component of your project and report statistics to you on which ones failed?
Can you automate regression testing?
Can you write your project using n languages and have them all compile together using a generic build process specified with build rules, using invocations of compilers (or your own developed tools) that the developers of the ide had never heard of?
Can you generate dependencies on source files and header files for languages that the ide developers don't use?
Can you accidentally delete your entire project by making a typo in your Makefile, or equivalent?
Can you accidentally overwrite your source files with the output of an automated test?
Can you employ conditional logic in your build process that is so complicated that the Makefile itself needs to be test so that it wont suddenly delete everything from a logic error in a corner case?
Can you write Makefiles to automate the testing of your other Makefiles?
Can you use logic in the build process that is so complicated that no one will ever be able to find out what is going wrong when the build process stops working?
Can you write a Makefile that will help figure out the behavior of another Makefile?
Can you use lisp as a part of your build process?
If you are able to do all of these things using your ide, then that's a cool ide. However, real programmers always run the risk of using a faulty makefile that destroys everything.