To IDE, or not to IDE

In this week's InfoWorld column ("The great IDE debate"), I discuss the timeless debate over the use of IDEs:

As a Java shop, we have our choice of dozens of tools to produce our code, but our developers have opted for the humble text editor. Our developers use a wide variety of text editors within the team (UltraEdit-32, vi, and Emacs), but each developer basically sticks to the simple text file environment. Our team is highly productive and probably the best at hitting deadlines that I have ever managed, but when it comes to writing code, IDEs (integrated development environments) just leave them cold.[read the rest here]

I also found some other writing that address the pros and cons of IDEs, either directly or somewhat tangentially:

• 10 Reasons to Dump Your Java IDE (Bradley S. O'Hearne)
• 10 Reasons (Not) to Dump Your Java IDE(Rafe Colburn)
• IDEs and their Projects (Tim Bray)
• NetBeans 4.0 Rocks! (James Gosling)