When comparing Eclipse vs Visual Studio Code, the Slant community recommends Visual Studio Code for most people. In the question“What are the best IDEs for the Go programming language?” Visual Studio Code is ranked 3rd while Eclipse is ranked 8th. The most important reason people chose Visual Studio Code is:
Ranked in these QuestionsQuestion Ranking
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, Eclipse is very customizable.
Pro Free and open source
Eclipse is an open source project and free to use.
Pro Fast compiler
Eclipse uses a custom compiler (which can also be used outside of Eclipse), which is often faster than the normal Java Compiler, especially for incremental compilation.
Pro Multiple languages - one IDE
Pro Good font rendering
Because Eclipse is based on SWT, it uses the native font rendering and thus looks better than other IDEs on some Linux systems, where the Java font rendering is not optimal.
Pro Great debugger
Shows threads, concurrency locks, and conditional breakpoints.
Pro Good refactoring tools
Pro Gives good perspectives on your project
The concept of perspectives is outstanding. It puts right tools at your fingertips, keeping the tools you currently don't need out from the workbench. For example, in VCS perspective it's all about versions and branches. In debug perspective it's all about state.
In java ee project it can show http endpoints in a very accessible manner.
Pro Extendable through plugins
Visual Studio Code comes fairly complete out of the box, but there are many plugins available to extend its functionality.
Pro TypeScript integration
There is very solid TypeScript integration in Visual Studio Code. Both are developed by Microsoft and VSC itself is written in TypeScript.
Pro Embedded Git control
Visual Studio Code has integrated Git control, guaranteeing speed, data integrity, and support for distributed, non-linear workflows.
Pro Integrated debugging
Pro Ready to use out of the box
You don't need to configure and add plugins before being productive. However, you can add plugins if needed but for the basics you're well covered.
Pro Integrated terminal
There's no need to press alt+tab to go to a terminal: it is directly integrated into the editor.
Shift+~ is a handy hotkey to toggle the integrated terminal.
Pro Great performance
For a 'wrapped' web-based application, Visual Studio Code performs very well.
Pro Updated frequently
There's a new release of Visual Studio Code every month. If you are one of the insiders then releases are daily.
Pro Integrated task runners
Task runners display lists of available tasks and performing these tasks is as simple as a click of the mouse.
Pro ESLint integration
ESLint integrates great. You can define your rules trough .eslintrc.* as usual and vs code will autofix your code on save. So your code is always in style.
Pro Libre/open source
Released under the MIT License.
Pro Active development
It's really nice to see how the code editor evolves. Every month there is a new version with great communication of new features and changes.
Pro Custom snippets support
Snippets are templates that will insert text for you and adapt it to their context, and in VSC they are highly customizable.
Pro Huge community behind it
The ease of getting assistance and finding tutorials is increasing as the community grows.
Pro Fast and powerful
VS-Code has the speed of Sublime and the power of WebStorm. Perhaps this is the best software that Microsoft has ever created.
Pro High fidelity C# plugin
The Omnisharp plugin is very powerful providing full sln, csproj, and project.json support.
Pro It has gotten really good
All it takes is one stop for all the features many people need.
Pro Support RTL languages
It supports pretty web rtl languages like arabic languages when most of other editors don't support it.
Pro JS typechecking
It leverages TypeScript compiler functionality to statically type check JS (type inference, JSDoc types) with
Pro Inline definition picking and usages finding
These features allow you to have a glance at code without opening it as a whole in a separate tab. Moreover, editing is allowed.
Pro Good support for new Emmet syntax
Pro Python support
Excellent Python plugin, originally created by Don Jayamanne, now hired by Microsoft to extend and maintain the extension.
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 UI can be confusing
There's an overly abundant presence of menus, this forces you to constantly click around the different menu structures; foreign ideas, like Views and Perspectives; strange menu choices, like configure settings located in Windows menu->Preferences.
Con Lack of plugins with good user interfaces
Many Eclipse plugins are extremely confusing, with UIs that are even less consistent than Eclipse itself.
Con Newer versions are getting less stable
Eclipse 4 Neon randomly hangs. For example, during installing new software.
Con Tends to be slow and lags a lot
Con Poor language support via plugins
Eclipse supports other languages with a huge amount of plugins. Many languages have their own distribution, but multi-language is hard to exist in one project. Like Scala, there is no official support from Eclipse for this language. If Eclipse gets an update, languages such as these will not.
Con Some old bugs don't get fixed
E.g. change a parameter name to the same as a field - the field will not be prefixed with "this." like in IDEA.
Con The autocomplete and code check is not as powerful as the one on WebStorm
Sometimes it doesn't tell you if you made a typo in a method name or if a method is not used and several other important features.
Con Very bad auto import
Con Embedded Git isn't powerful enough
You can do nothing but to track changes, stage them and commit. No history, visualization, rebasing or cherry-picking – these things are left to git console or external git client.
Con Project search limits results
Because file search is so slow your results are limited in order to simulate a faster search.
Con No support for tiled/grid editor layouts
It can be configured for rows of editors, or columns of editors, but not both simultaneously. The development team has explicitly said this is not a priority.
Con Is not an IDE, is a text editor
VS Code is a general code/scripting IDE built to be lightweight and for people familiar with their language of choice, not directly comparable to Visual Studio in power or scope.
Con Memory hog
Allegedly, VS Code is "lightweight". Yet, running multiple instances of it at once, you may get many "out of memory" messages from Windows despite 16 GB RAM. (While of course also running other things. The point is the comparison with some other IDEs/editors where running them alongside the same number of other applications doesn't cause Windows to run out of memory)
Con A "me too" offering from MS, far behind other well established editors that it attempts to clone
Other IDEs specific to a language often offer better tools for deep programming.
Con Have no good default js style analyzer
In WebStorm there is analyzer that checks for warnings and highlight this in yellow, here I cannot find or add it even with plugins. It is possible to have it as errors with linter but while you are actively changing file that's not very nice.
Con Slow launch time
Than it's competitors, e.g. Sublime Text.
Con Emmet plugin often fails on even simple p tags
Con File search is extremely slow
It's absolutely not possible to use this tool with big projects given how long it takes to search for files.