When comparing Kakoune vs Eclipse Che, the Slant community recommends Kakoune for most people. In the question“What are the best open-source text editors for programming?” Kakoune is ranked 11th while Eclipse Che is ranked 20th. The most important reason people chose Kakoune is:
Kakoune first started as a rewrite from scratch of vim, but then ended up being another text editor altogether. So it's inspired in a lot of ways from vim.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Will be familiar to vim users
Kakoune first started as a rewrite from scratch of vim, but then ended up being another text editor altogether. So it's inspired in a lot of ways from vim.
Pro More modern than vim
Pro Good UNIX citizen
It follows the UNIX philosophy by doing one thing well (text editing) and interfaces nicely with other CLI tools.
Pro Text selection mechanism
Kakoune works on selections, which are oriented, inclusive range of characters, selections have an anchor and a cursor character. Most commands move both of them, except when extending selection where the anchor character stays fixed and the cursor one moves around.
Pro Very expressive
Kakoune provides a very expressive set of commands, including various objects selection (paragraph, blocks, words), alignment support, conditional selection filtering...
This set of command is expressive enough to implement all the provided auto indentation logic.
Pro Actively developed and supported
Pro Self-documenting
A helper pops up when typing commands.
Pro Simpler and more consistent than Vim
Some keys select, other keys operate on the selections. Shift
is used to extend the selection, alt
is used for alternative behavior, e.g. reverse the search direction. No inconsistencies like Y
which means yy
and not y$
in Vim.
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
Cons
Con Small community
Con No real Windows support
Will compile under CygWin.
Con Default bindings do not play nice with OS X (Alt+???)
Con Written in C++
Con Slow runtime
Online IDE is much slower than desktop one.