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

结构搜索和替换。

例如，搜索如下内容:

  System.out.println($string$ + $expr$);

其中$string$是一个文字，$expr$是my.package.and.Class类型的表达式，然后替换为:

  $expr$.inspect($string$);

多得多的重构。

对我来说，它是IDEA的maven支持，特别是在版本9中是首屈一指的。项目与maven模型的动态同步非常棒，使开发变得愉快。

IntelliJ做了而Eclipse没有做的两件事对我来说非常有价值:

方法分隔符:方法之间那些模糊的灰色线条使代码更具可读性

文本抗锯齿:使代码在IDE中看起来很漂亮

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