When comparing IntelliJ IDEA vs Eclipse with JSDT, the Slant community recommends IntelliJ IDEA for most people. In the question“What are the best JavaScript IDEs or editors?” IntelliJ IDEA is ranked 7th while Eclipse with JSDT is ranked 34th. 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.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
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 Support for many languages
IntelliJ supports many languages besides Java, some of these are: golang, Scala, Clojure, Groovy, Bash, etc.
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 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 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 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 Gradle support
Pro Built-in Git support
Pro Student Benefits
Verify yourselves as a student to get more perks.
Pro Embedded database support
Creating an embedded database, running SQL script in a dedicated terminal, viewing tables and their contents, and creating a connection to an in-memory or embedded database is fully supported.
Pro Prices are not bad
I pay $24 a month and i have access to all jetbrain peoducts , so i use their many tools , i tried many others like netbeans , eclipse , etc , they re good but intelij is on the space and the sky is the limit . Been using it for 5 years and i cant tell i got frustrated using .it
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 Slow startup
Startup can be slow depending on system configuration.
Con Uses a lot of RAM
Con Somewhat expensive
IntelliJ IDEA is fairly expensive, with a pricetag of $149/year.
However there is a free community edition available.
Con Built with closed source components
The version with full features is not opensource. Parts of the code are under apache licence though.
Con Cannot open multiple projects in the same window
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 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 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 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.