Komodo IDE vs Eclipse

Since Version Control features are very frequently used these days, having them built right into your IDE seems quite the right thing to do. With Komodo, you can perform your Git push-es and pull-s right while you're coding.

If you're working with a remote dev team, you'll quickly realize the importance of code collaboration while programming. With the Komodo IDE you don't have to setup a separate teamviewer session, or even share code via dropbox with other devs. All you need is an ActiveState account (+ a partner with the KomodoIDE ofcourse) and your remote team could see LIVE and contribute to your changes in the source files of your app

Eclipse is an open source project and free to use.

Eclipse has a large and active community, which has resulted in a wide variety of plugins.

Eclipse uses a custom compiler (which can also be used outside of Eclipse), which is often faster than the normal Java Compiler, especially for incremental compilation.

It's interface is super easy to use, after adding required package for your task everything just works.

The concept of perspectives is outstanding. It puts right tools at your fingertips, keeping the tools you currently don't need out from the workbench. For example, in VCS perspective it's all about versions and branches. In debug perspective it's all about state.
In java ee project it can show http endpoints in a very accessible manner.

Thanks to the large variety of plugins and various configuration options, Eclipse is very customizable.

Shows threads, concurrency locks, and conditional breakpoints.

Because Eclipse is based on SWT, it uses the native font rendering and thus looks better than other IDEs on some Linux systems, where the Java font rendering is not optimal.

Fast, suitable for big projects, customizable, supports UML, many programming languages, plugins, and widgets vs NetBeans and JDeveloper. Support for Workspaces and Perspectives. Long term tested, free of charge, vs IntelliJ IDEA.