When comparing Eclipse Che vs Koding, the Slant community recommends Koding for most people. In the question“What are the best cloud IDEs?” Koding is ranked 3rd while Eclipse Che is ranked 8th. The most important reason people chose Koding is:
All languages, databases, and command-line tools are supported. Most machines are already set up with web project basics like Apache, PHP, MySQL, Ruby, Node.js, Perl, and Python and anything else can be installed via the SSH root access.
Specs
Ranked in these QuestionsQuestion Ranking
Pros

Pro SSH + terminal
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.

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

Pro Docker runtimes
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.
Pro GIT and SVN VCS support
Projects can be easily imported from any Git or Svn repository hosting service.
Pro Reproducible environment

Pro Portable workspaces
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.

Pro Previews
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.
Pro Merge tool for VCS

Pro Open-source
Pro Everything is supported
All languages, databases, and command-line tools are supported. Most machines are already set up with web project basics like Apache, PHP, MySQL, Ruby, Node.js, Perl, and Python and anything else can be installed via the SSH root access.
Pro Ability to signup with Github
And link account to oDesk and Facebook.
Pro Great community
Koding has a community feature that makes it easy to collaborate and share ideas with like minded developers all over the world. And the community itself is very active and helpful community.
Pro Real-time collaboration
Real-time code and terminal collaboration with integrated chat abilities.
Pro Built-in terminal
With 256-color support.
Pro Various file upload options
Koding supports drag & drop, Dropbox, clone from Github, FTP and the ability to access them using SSH.
Pro Built-in package manager
The Koding Package Manager (a successor to Apps) is command line tool for installing packages like nginx, Redis, VNC, Wordpress and many others. It consists of officially supported and user-built packages.
Pro Communities
Ability to create different sized communities that can be public or private.
Pro Social Stream
There's a built-in social network with developers from all over the world.
Pro Unlimited domains and subdomains
Unlimited user-defined domains and subdomains for private or shared VMs can be set up.
Pro Capable editor
Koding uses the Ace editor that's developed by Cloud9. Besides the basics, it covers most important advanced code editor features such as code folding, converting cases, auto-completion, code analysis and refactoring, regex search and offers easy access to relevant documentation.
It also gives access to the CLI, has support for Vim and Emacs keybindings, includes multiple cursors and zen coding mode that removes all distractions and allows focusing on code.
Cons
Con Slow runtime
Online IDE is much slower than desktop one.
Con Not a cloud IDE
Have to provide your own IDE, so not a cloud IDE.
Con No real individual user support
While they do have plans available for 1-10 users, they are not focused on individual developers, so much as teams.
