其他一些事情:

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

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

例如，两者都有编辑器围绕码头面板的项目，类路径，输出，结构等。但在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正在处理这个问题。

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

我经常使用的一件事是设置断点，然后控制它的功能。(在我的上一份工作中，大多数人都使用Eclipse……我记得我很惊讶，没有人能在Eclipse中找到如何做到这一点。)

例如，可以让断点实际上不停止，而只是将消息记录到控制台。这意味着，我不必用“System.out.println(…)”乱写代码，然后重新编译。

有很多事情是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的用户群将呈指数级增长。

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

如果你把光标放在一个方法上，然后按CTRL+SHIFT+I将弹出方法实现。如果方法是一个接口方法，那么你可以使用上下箭头来循环实现:

Map<String, Integer> m = ...
m.contains|Key("Wibble");

|的位置(例如)您的光标所在的位置。