Komodo IDE vs Eclipse Che

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

Built-in terminal with root access so you can make changes to your running machines. Being able to SSH into the workspace so you can use a desktop IDE is handy.

You can package up custom commands with your workspace and then use them (or share them) with everyone else.

You can choose from pre-configured environments for Java, Javascript, C++, PHP, C#, etc., or you can define your own by dropping in a Dockerfile - makes it easy for simple and complex projects.

Projects can be easily imported from any Git or Svn repository hosting service.

The workspace in Che includes project sources, IDE and the runtime. So if you hand your Che workspace definition to another user and they execute it they will get everything they need to build, run and debug the project.

Also the runtime is in a Docker container so it will work even if the second user is on a different OS than the original user who shared their workspace with them.

Che does a nice job to automatically map the service:port running in the Docker container (e.g. tomcat on 8080) to the Docker port it actually uses (something in the ephemeral range). You never need to figure that out - it's just made available when you run your server.