-ctrl-click on a varible or type to see the code automatically and not have to go through tons of directory hunting for it. This is a huge timesaver.

-ctrl-shift-t / ctrl-shift-r are similar to the ctrl-click

-Auto-complete/Inline-documentation can be an enormous timesaver and you don’t find it in non-ide type editors like textmate.

-Inline error & warning higlighter & problem’s browser. If I make a mistake, it’s highlighted right away. It of course doesn’t catch all problems, but it catches a lot of the small goofups that can really consume time when you forgot that semi-colon or something similar and have to go through another save-build-run-wait-wait-wait-error to have the problem blow up in your face.
-A full featured debugger.
-Litter your code with TODO comments and you have an automatic todo list!
- The code outline can be useful at times (although textmate has this one)
- The easy to use multi-directory/file diffing tools
- The built in scm management tools — Occasionally, I also use the save history tools built in for more granular reverting.
- And the basic features you mentioned.

There are several features that I would use in eclipse, but don’t work with our particular software setup (we use the obscure resin server w/ struts 1.1 vs. tomcat w/ spring for example, which remove a bunch of eclipse feature ), or there are better tools to deal with the specific part, like cssedit2 for css editing.

We don’t use the profiler since we don’t really have speed problems with our web apps.

The only really bad thing about eclipse is it’s heavyweight nature. If eclipse wasn’t memory and processor intensive and was developed with a better gui, would you really care about using eclipse? No! It would completely pure awesome. Are there new features you can use to improve it? Of course!