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中可以做的大部分事情，但它花费的时间更长，而且更笨重。

数据流分析:如本文所述，过程间的反向流分析和正向流分析。我的经验是基于Community Edition，它在数据流分析方面做得相当好。当代码非常复杂时，它在少数情况下会失败(拒绝做任何事情)。

IntelliJ具有从代码到jspx文档的智能感知和重构支持。

IntelliJ调试器有一个非常方便的特性，叫做“表达式计算”，这比eclipses pendant好得多。它有完整的代码完成，我认为它通常“更有用”。

一个非常有用的特性是能够部分构建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的前端。

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

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

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

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