When comparing Eclipse vs Eclipse Che, the Slant community recommends Eclipse Che for most people. In the question“What are the best Java IDEs?” Eclipse Che is ranked 4th while Eclipse is ranked 5th. The most important reason people chose Eclipse Che is:
Ranked in these QuestionsQuestion Ranking
Pro Fast compiler
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.
Pro Large selection of plugins
Eclipse has a large and active community, which has resulted in a wide variety of plugins.
Pro Highly customizable
Thanks to the large variety of plugins and various configuration options, Eclipse is very customizable.
Pro Free and open source
Eclipse is an open source project and free to use.
Pro Multiple languages - one IDE
Pro Good font rendering
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.
Pro Great debugger
Shows threads, concurrency locks, and conditional breakpoints.
Pro Good refactoring tools
Pro Gives good perspectives on your project
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.
Pro Docker runtimes
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 GIT and SVN VCS support
Projects can be easily imported from any Git or Svn repository hosting service.
Pro Reproducible environment
Pro Custom commands
You can package up custom commands with your workspace and then use them (or share them) with everyone else.
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.
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
Con Plugins can be unstable
Though there are plenty of plugins to choose from, they aren't always reliable. Some aren't maintained, bug fixes can be slow, and you may need to download plugins from multiple sources.
Con UI can be confusing
There's an overly abundant presence of menus, this forces you to constantly click around the different menu structures; foreign ideas, like Views and Perspectives; strange menu choices, like configure settings located in Windows menu->Preferences.
Con Lack of plugins with good user interfaces
Many Eclipse plugins are extremely confusing, with UIs that are even less consistent than Eclipse itself.
Con Newer versions are getting less stable
Eclipse 4 Neon randomly hangs. For example, during installing new software.
Con Tends to be slow and lags a lot
Con Poor language support via plugins
Eclipse supports other languages with a huge amount of plugins. Many languages have their own distribution, but multi-language is hard to exist in one project. Like Scala, there is no official support from Eclipse for this language. If Eclipse gets an update, languages such as these will not.
Con Some old bugs don't get fixed
E.g. change a parameter name to the same as a field - the field will not be prefixed with "this." like in IDEA.
Con Slow runtime
Online IDE is much slower than desktop one.