两者有许多不同的特性和工作流程，这在所有的答案中都很明显。然而，我认为在决定使用哪种框架时，也应该考虑使用每种工具所能提高的总体生产力。

我是Netbeans和Eclipse的忠实粉丝，并且已经使用它们很多年了。它们都是很好的工具，根据您正在做的事情，您可能想要选择其中一个。

然而，大约六个月前，当我在一个复杂的java web项目中工作时，由于js的自动完成错误，我被迫寻找Eclipse的替代品。我是如此绝望，我正在考虑回到一个简单的文本编辑器为我的js代码!!

我只是碰巧遇到了Intellij Idea(不幸的是没有时间研究工具)。

虽然需要一些时间来适应Idea的做事方式，除了特殊的功能之外，在我看来，它从左到右的小事情上提供的生产力提高是最大的资产。它更适合我，我现在是Idea Ultimate的付费客户。一旦你习惯了这一点，就很难再去做别的事情了。

没有什么比免费更好的了，我是开源的忠实粉丝，但最终如果你以开源为生，那么每次都能更快地完成任务。

有很多事情是idea用更简单的方法解决的，或者没有等价的方法:

Autocomplete actions: Doing ctrl+shift+a you can call any idea action from the keyboard without remembering its key combination... Think about gnome-do or launchy in windows, and you've got the idea! Also, this feature supports CamelCasing abbreviations ;) Shelf: Lets you keep easily some pieces of code apart, and then review them through the diff viewer. Local history: It's far better managed, and simpler. SVN annotations and history: simpler to inspect, and also you can easily see the history only for such a part of a whole source file. Autocomplete everywhere, such as the evaluate expression and breakpoint condition windows. Maven integration... much, much simpler, and well integrated. Refactors much closer to the hand, such as loops insertion, wrapping/casting, renaming, and add variables. Find much powerful and well organized. Even in big projects Much stable to work with several branches of a big project at the same time (as a former bugfixer of 1.5Gb by branch sources, and the need to working in them simultaneously, idea shown its rock-solid capabilities) Cleaner and simpler interface... And, simpler to use only with the keyboard, letting apart the need of using the mouse for lots of simple taks, saving you time and giving you more focus on the code... where it matters!

现在，作为开源的…Idea的用户群将呈指数级增长。

抱歉，如果这已经涵盖了，但简单地有“变化”标签在那里，我可以看到我的本地变化，传入的变化，远程变化只是简单的东西，我不能没有。在Eclipse中，我找不到这样的特性!

另外，像中间点击绑定到“开放声明”这样简单的事情是一个很好的UI添加——我也看不到在Eclipse中实现的东西。

在我工作的地方只有Eclipse，但我正在认真考虑购买个人的Idea许可证....

Well, for me it's a thousand tiny things. Some of the macros, the GUI layout in general in Eclipse I find awful. I can't open multiple projects in different windows in Eclipse. I can open multiple projects, but then it's view based system swaps a bunch of things around on me when I switch files. IntelliJ's code inspections seem better. Its popup helpers to fix common issues is nice. Lots of simple usability things like the side bar where I can hover over a hot spot and it'll tell me every implementing subclass of a method or the method I'm implementing and from where.

每当我不得不使用Eclipse时，或者看到别人使用Eclipse时，他们似乎可以做我在IntelliJ中可以做的大部分事情，但它花费的时间更长，而且更笨重。

IntelliJ有一些相当高级的代码检查(与FindBugs类似但又不同)。

虽然我在使用IntelliJ时非常想念FindBugs插件(Eclipse/FindBugs集成非常酷)。

下面是IntelliJ支持的代码检查的官方列表

编辑:最后，IntelliJ有一个findbugs-plugin。它仍处于测试阶段，但代码检查和FindBugs的组合非常棒!

一个非常有用的特性是能够部分构建Maven反应堆项目，以便只包括您需要的部分。

To make this a little clearer, consider the case of a collection of WAR files with a lot of common resources (e.g. JavaScript, Spring config files etc) being shared between them using the overlay technique. If you are working on some web page (running in Jetty) and want to change some of the overlay code that is held in a separate module then you'd normally expect to have to stop Jetty, run the Maven build, start Jetty again and continue. This is the case with Eclipse and just about every other IDE I've worked with. Not so in IntelliJ. Using the project settings you can define which facet of which module you would like to be included in a background build. Consequently you end up with a process that appears seamless. You make a change to pretty much any code in the project and instantly it is available after you refresh the browser.

非常简洁，而且非常快。

我无法想象在没有它的情况下，在像YUI这样的东西中编写一个返回到DWR/SpringMVC的前端。