When comparing IntelliJ IDEA vs Eclipse Che, the Slant community recommends IntelliJ IDEA for most people. In the question“What are the best IDEs for Android development?” IntelliJ IDEA is ranked 1st while Eclipse Che is ranked 8th. The most important reason people chose IntelliJ IDEA is:
IDEA places an emphasis in safe refactoring, offering a [variety of features](https://www.jetbrains.com/idea/features/refactoring.html) to make this possible for a variety of languages. These features include safe delete, type migration and replacing method code duplicates.
Ranked in these QuestionsQuestion Ranking
Pro Smart refactorings
IDEA places an emphasis in safe refactoring, offering a variety of features to make this possible for a variety of languages.
These features include safe delete, type migration and replacing method code duplicates.
Pro Fast and smart contextual assistance
Uses a fast indexing technique to provide contextual hints (auto-completion, available object members, import suggestions).
On-the-fly code analysis to detect errors and propose refactorization.
Pro Android support, JavaEE support, etc
A very complete development environment support.
Pro Lots of plugins
Many plugins are available for almost any task a developer may need to cover. Plugins are developed by Jetbrains themselves or by 3rd parties through the SDK available for writing them.
Pro Stable and robust
IntelliJ IDEA hardly ever crashes or has any issues that plague other Java IDEs like file corruption or slowness.
Pro Support for many languages
IntelliJ supports many languages besides Java, some of these are: golang, Scala, Clojure, Groovy, Bash, etc.
Pro Intuitive and slick UI
IDEA has a clean, intuitive interface with some customization available (such as the Darcula theme).
Pro Clear and detailed documentation
The documentation is exhaustive, easy to navigate, and clearly worded.
Pro Free version available
There is a free community edition (open source) and an ultimate edition, which you can compare here.
The ultimate edition is available for free for one year for students but must be registered through an .edu e-mail account.
Pro Many convenient features
These simplify the daily work, e.g. copy/cut a whole line without the need to select it.
Pro Very powerful debugger
With ability to step into a certain part of a large method invocation (Shift+F7), drop frame, executing code snippets, showing method return values, etc.
Pro Buit-in Git support
Pro Gradle support
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 Uses too much RAM
Con Slow startup
Startup can be slow deepending on system configuration
Con Bugs are not solved as often as they should
They are more interested in adding new features or issuing new versions than solving bugs.
Con Cannot open multiple projects in the same window
Con Built with closed source components
The version with full features is not opensource. Parts of the code are under apache licence though.
Con Standard hotkeys behave differently
Seems like hotkeys assignment in Idea has no logical consistency.
Like «F3» is usually next match, «Ctrl+W» - close tab, etc — they map to some different action by default.
There is a good effort in making the IDE friendly for immigrants from other products: there are options to use hotkeys from Eclipse, and even emacs. But these mappings are very incomplete. And help pages do not take this remapping into account, rather mentioning the standard hotkeys.
So, people coming from other IDEs/editors are doomed to using mouse and context menus (which are rather big and complex).
Con Lack of plugins
IntelliJ supports a very small amount of plugins. Although these are 'quality approved', many features are missing and can't be implemented because of that.
Con Slow runtime
Online IDE is much slower than desktop one.