When comparing Visual Studio Code vs Visual Studio, the Slant community recommends Visual Studio Code for most people. In the question“What are the best Git clients for Windows?” Visual Studio Code is ranked 4th while Visual Studio is ranked 16th. The most important reason people chose Visual Studio Code is:
Visual Studio Code comes fairly complete out of the box, but there are many plug-ins available to extend its functionality.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Extendable through plug-ins
Visual Studio Code comes fairly complete out of the box, but there are many plug-ins 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 Integrated debugging
VSC includes debugging tools for Node.js, TypeScript, and JavaScript.
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 Libre/open source
Released under the MIT License.
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 JavaScript IntelliSense support
JavaScript IntelliSense allows Visual Studio Code to provide you with useful hints and auto-completion features while you code.
Pro Embedded Git control
Visual Studio Code has integrated Git control, guaranteeing speed, data integrity, and support for distributed, non-linear workflows.
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 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 Extensions (aka plugins) are written in JavaScript
Extensions are written in either Typescript or JavaScript.
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 Integrated task runners
Task runners display lists of available tasks and performing these tasks is as simple as a click of the mouse.
Pro It has gotten really good
All it takes is one stop for all the features many people need.
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 JS typechecking
It leverages TypeScript compiler functionality to statically type check JS (type inference, JSDoc types) with "javascript.implicitProjectConfig.checkJs": true
option.
Pro Python support
Excellent Python plugin, originally created by Don Jayamanne, now hired by Microsoft to extend and maintain the extension.
Pro Good support for new Emmet syntax
Pro High fidelity C# plugin
The Omnisharp plugin is very powerful providing full sln, csproj, and project.json support.
Pro Support RTL languages
It supports pretty web rtl languages like arabic languages when most of other editors don't support it.
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 Official IDE developed by Microsoft
If a project type or a platform is available for C#, it's available in Visual Studio. Some IDEs and code editors may cover some project types, but Microsoft always starts with VS. If you work with a cross-platform technology like ASP.NET MVC, it matters less. If you work with Windows-only technologies like UWP or WPF, you have no choice really.
Pro Free Community edition
Community edition is almost Pro edition, with just a few exceptions. Unlike old Express editions, it supports plugins.
Pro Amazing coverage over languages
Supports many types of C, and java, as well as ruby and python.
Pro Excellent and broad range of plugins
The plugin development ecosystem is very mature and covers a lot of use cases. For example, it is often easy to find a plugin which allows you to have the keybindings of your preferred editor.
Pro Partial cross-platform support
Visual Studio runs on Windows and macOS, so even if you develop on a Mac you can still develop with Visual Studio.
Pro It can run c#, c++, etc.
You can use too many programming lang. And you can select them! Like "I want to do this, not this".
Pro Cloud storage
Your Visual Studio Online account gives you a place to store your code, backlog, and other project data with no servers to deploy, configure, or manage.
Pro Supported by ReSharper and other plugins
Code productivity tools improve code editing experience greatly, provide static code analysis, refactorings, navigation etc. They are considered by many developers as essential.
Pro Fast-paced development iteration
Fast-paced development iteration from the Microsoft team, with new versions and fixes almost every week.
Pro Comes With the .NET Framework
Pro Product backlog
In agile development teams one really needs features such as product backlogs where you can assign features to team mates and track their progress on them. VS provides a web based interface for you to track your team's complete progress on the project.
Pro Fast
Pro Time travel in debugging
Pro Great UI for nugget packages
Pro Flexible to install/adjust payloads
Pro Same excellent Roslyn compiler/editor as VS for Code + powerful debugging tools
Pro Good support and community
Pro sda
Cons
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 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 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.
Con Project search limits results
Because file search is so slow your results are limited in order to simulate a faster search.
Con Very bad auto import
Con Generalized
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 Poor error fix suggestions
Error detection and suggestions/fixes are poor compared to IntelliJ platforms
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 Slow launch time
Slower than it's competitors, e.g. Sublime Text.
Con Emmet plugin often fails on even simple p tags
Con Have no good default js style analyzer
In WebStorm there is analyzer that checks for warnings and highlight this in yellow, here you 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 .sass linting is terrible
Con Is not an IDE, is a text editor
Con Slow & Buggy (on Mac)
Visual Studio can get very slow on Mac... this is partly due to bad UI framework used - GTK. Also, quite buggy and too often have to Force Quit and restart.
Con Professional pricing is a bit steep
The professional edition's pricing is endearing since it costs more than IntelliJ, however, you wouldn't need that if you're not developing for a enterprise.
Con No Linux version
Con Mac version sub-par
The Mac version has the same great Roslyn editor as Win and VS for Code.
Con Too much storage eater for low-end PCs
For a particular task, you need to install workspaces. Workspaces mainly take up to 50 GB.
