When comparing Kakoune vs Eclipse with JSDT, the Slant community recommends Kakoune for most people. In the question“What are the best JavaScript IDEs or editors?” Kakoune is ranked 27th while Eclipse with JSDT is ranked 34th. 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 Provides quick fixes
Eclipse with JSDT provides you with quick fixes every time a warning or error is raised by the IDE. This feature is particularly helpful at places in code where errors were caused by the programmer just being a little "lazy", such as missing out the +
sign between two operands or a variable being out of scope.
Pro Smart Code completion
Just like all other IDEs, Eclipse offers you inline code completion (even with any external JS libraries added to the project).
Pro Free and cross-platform
Eclipse runs on Windows, Linux and Mac, and is totally free of cost.
Pro Code refactoring
Eclipse's refactoring features are quite similar to Webstorm's. It provides almost the same functionalities which include renaming, moving, and member extraction to make your code tidier
Pro Code auto-completion for brackets and parenthesis
This feature is particularly useful when you've added a lot of nesting in your code and you're unable to recall which opening bracket corresponds to which closing one.
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 available, Eclipse is very customizable.
Pro Seamless integration with web servers like Apache or Jetty
Eclipse lets you integrate web servers (like Apache or Jetty) into the IDE, which you could use for in-container testing or providing services.
Pro Good integration with git using eGit plugin
Pulling, pushing, staging, stashing, etc., are all available in Eclipse as IDE functionalities.
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 Uses a lot of memory
Eclipse hogs a lot of memory, although this can be controlled by the IDE start-up ini file.
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 Support and problem solving is difficult to find
The Eclipse forums have more tumbleweed than users. Stack-overflow also has very little info.