When comparing SlickEdit 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 SlickEdit is ranked 9th. The most important reason people chose Eclipse Che is:
Ranked in these QuestionsQuestion Ranking
Pro Symbol analysis support
There are powerful symbol analysis features in SlickEdit, including context tagging and references.
Pro Extensive support for programming languages
SlickEdit supports over 50 programming languages on nine platforms.
Pro Integrated debuggers for multiple languages
Integrated debuggers for GNU C++, Java, Python, Perl, Ruby, and PHP.
Pro Built-in beautifier
The beautifier formats code as you type to help improve readability and consistency.
Pro Compiler tools
Pro Over 13 emulations
Choose from fifteen keyboard emulations, containing the key bindings and behaviors necessary to emulate other editors (e.g., CUA, Vim, GNU Emacs, etc.)
Windows, Linux, Mac OS X, AIX, HP-UX, Solaris SPARC, Solaris x86
Pro Portable mode
Possibility to set up a portable installation, to run on a USB drive for example.
Write custom macro commands, functions, dialogs and tool windows.
Pro Easy access to XCode projects
SlickEdit opens XCode projects with no conversions needed.
Pro Third party tool integration
Pro Easy access to Visual Studio workspace
SlickEdit opens Visual Studio workspace with no conversions needed.
Pro Popular version control system
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 Slow runtime
Online IDE is much slower than desktop one.