其他一些事情:

propagate parameters/exceptions when changing method signature, very handy for updating methods deep inside the call stack SQL code validation in the strings passed as arguments to jdbc calls (and the whole newly bundled language injection stuff) implemented in/overwritten in icons for interfaces & classes (and their methods) and the smart implementation navigation (Ctrl+Alt+Click or Ctrl+Alt+B) linking between the EJB 2.1 interfaces and bean classes (including refactoring support); old one, but still immensely valuable when working on older projects

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

可能不是能做/不能做的问题，而是如何做的问题。

例如，两者都有编辑器围绕码头面板的项目，类路径，输出，结构等。但在Idea中，当我开始输入所有这些自动折叠时让我专注于代码本身;在eclipse中，所有这些面板都保持打开，使我的编辑器区域非常小，大约是总可视区域的1/5。所以我必须抓住鼠标，点击来最小化这些面板。在日食中，整天这样做是一种非常令人沮丧的经历。

The exact opposite thing happens with the view output window. In Idea running a program brings the output window/panel to see the output of the program even if it was perviously minimized. In eclipse I have to grab my mouse again and look for the output tab and click it to view my program output, because the output window/panel is just another one, like all the rest of the windows, but in Idea it is treated in a special way: "If the user want to run his program, is very likely he wants to see the output of that program!" It seems so natural when I write it, but eclipse fails in this basic user interface concept.

可能在eclipse中有一个快捷方式(编辑时自动隐藏输出窗口，运行程序时自动显示)，但由于其他几十个功能，快捷方式必须在论坛，在线帮助等中寻找，而在Idea中则更“自然”一些。

这可以重复几乎所有的功能，自动完成，自动换行，快速文档查看，一切。我认为在Idea中的用户体验要比在eclipse中的用户体验愉快得多。那么，“快乐地发展”这句格言就成为现实了。

Eclipse可以处理更快的大型项目(+300个jar和+4000个类)，我认为IntelliJ Idea 8正在处理这个问题。

当然，所有这些都是主观的。我们如何衡量用户体验?

我没有用IntellijIdea编写过很多代码，但是在IntellijIdea中，你可以看到括号(if, try/catch, cycle等)之间的代码块在哪里开始，在哪里结束。

在Eclipse中(我在Eclipse 3.2中编码)，您只能手动识别块。

有一件事IntelliJ做得比Eclipse好得多，那就是清空你的口袋!

然而，我确实更喜欢使用它，它比Eclipse有一个很大的优势，就是它与文件系统同步的方式，对于大项目和慢速的计算机(是的，在工作环境中，PC的速度比我们家里的慢得多)，Eclipse似乎与IntelliJ相比似乎更快，尽管初始索引时间较慢。

IntelliJ社区版显然可以免费使用它，但你很快就会想要那些额外的重构和CC版不包含的小东西。

在我看来，这通常是一个更好的用户体验，但是否值得这个成本是每个开发者自己要回答的问题。

但是让我们感激我们现在有三个很棒的Java ide, NetBeans一直在变得更好。

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