Eclipse:

代码高亮显示，在后台编译，在执行过程中指出错误。

与javadoc集成，使用ctrl-Space提示变量名。

当我编译时，就会得到错误。我可以双击一个错误，它会显示相应的行。

很好地与JUnit集成，ctrl-F11运行测试，告诉我测试失败了。如果在输出窗口中出现异常，我可以双击某行，并将我带到失败的行。不仅如此，ctrl-F11还可以确保在运行测试之前编译所有内容(这意味着我永远不会忘记这样做)。

与ant集成。一个命令用于构建和部署应用程序。

集成调试器，包括web服务器的远程调试。

神奇的重构工具，搜索一段代码的引用。帮助我了解改变的影响。

总而言之，这让我更有效率。

代码自动完成。它对探索代码有很大帮助。

ide基本上是:

编辑器/代码完成，重构和文档 调试器 文件系统资源管理器 scm的客户 构建工具

都在一个包里。

您可以使用单独的工具或出色的可编程编辑器和额外的工具，如Emacs(也可以使用Vim，但IDEbility IMO稍微少一些)来实现所有这些功能(以及更多功能)。

如果您发现自己经常在一个实用程序和下一个可以集成到环境中的实用程序之间切换，或者如果您缺少这里列出的一些功能(其他文章中有更完整的功能)，那么可能是时候转移到IDE了(或者通过添加宏之类的方法来提高环境的ideability)。如果你已经用一个以上的程序构建了一个“IDE”(在我上面提到的意义上)，那么就没有必要转移到一个真正的IDE。

作为你在你的问题中强调的回答的作者，并且承认这一点有点晚了，我不得不说，在列出的许多原因中，专业开发人员的生产力是最受重视的技能之一。

我所说的生产力是指高效地完成工作并取得最佳结果的能力。ide在许多级别上都支持这一点。我不是Emacs专家，但我怀疑它缺乏主要ide的任何特性。

设计、文档编制、跟踪、开发、构建、分析、部署和维护，这些企业应用程序中的关键步骤都可以在IDE中完成。

如果你有选择，为什么不用这么强大的东西呢?

作为实验，让自己使用一个IDE 30天，然后看看感觉如何。我很想听听你对这次经历的看法。

我从相反的方向来回答这个问题。我从小就在Makefile+Emacs的环境中编程。从我最早的DOS编译器，微软的Quick C，我有一个IDE自动化的事情。我在Visual c++ 6.0上工作了很多年，当我毕业到Enterprise Java时，我使用Borland JBuilder，然后决定使用Eclipse，这对我来说已经变得非常高效。

Throughout my initial self-teaching, college, and now professional career, I have come to learn that any major software development done solely within the IDE becomes counterproductive. I say this because most IDE's wants you to work in their peculiar I-control-how-the-world-works style. You have to slice and dice your projects along their lines. You have manage your project builds using their odd dialog boxes. Most IDE's manage complex build dependencies between projects poorly, and dependencies can be difficult to get working 100%. I have been in situations where IDE's would not produce a working build of my code unless I did a Clean/Rebuild All. Finally, there's rarely a clean way to move your software out of development and into other environments like QA or Production from an IDE. It's usually a clicky fest to get all your deployment units built, or you've got some awkward tool that the IDE vendor gives you to bundle stuff up. But again, that tool usually demands that your project and build structure absolutely conforms to their rules - and sometimes that just won't work for your projects' requirements.

我了解到，要与团队一起进行大规模开发，如果我们使用IDE开发代码，并使用手动编写的命令行脚本进行所有构建，那么我们可以获得最高的效率。(我们喜欢用Apache Ant进行Java开发。)我们发现在IDE中运行我们的脚本对于复杂的构建来说只是一个点击或者自动化的噩梦，用alt+tab到一个shell并在那里运行脚本要容易得多(而且破坏性更小)。

Manual builds requires us to miss out on some of the niceties in the modern IDE like background compilation, but what we gain is much more critical: clean and easy builds that can live in multiple environments. The "one click build" all those agile guys talk about? We have it. Our build scripts can be directly invoked by continuous integration systems as well. Having builds managed through continuous integration allows us to more formally stage and migrate your code deployments to different environments, and lets us know almost immediately when someone checks in bad code that breaks the build or unit tests.

In truth, my taking the role of build away from the IDE hasn't hurt us too badly. The intellisense and refactoring tools in Eclipse are still completely useful and valid - the background compilation simply serves to support those tools. And, Eclipse's peculiar slicing of projects has served as a very nice way to mentally break down our problem sets in a way everyone can understand (still a tad bit verbose for my tastes though). I think one of the most important things about Eclipse is the excellent SCM integrations, that's what makes team development so enjoyable. We use Subversion+Eclipse, and that has been very productive and very easy to train our people to become experts at.

IDE处理繁重的工作，节省了您的时间。

它将所有相关的项目文件保存在一起，使协作变得容易。

您通常可以将源代码控制集成到IDE中，从而节省更多的繁重工作，并进一步增强协作。

如果它有自动完成功能，它可以帮助你探索你所选择的语言，还可以节省一些输入。

基本上，IDE减少了程序员的非编程工作。