When comparing Visual Studio Code vs GitExtensions, 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 GitExtensions is ranked 7th. 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 Open source
It's totally free
And its written and thought by developers who really know what you need as a developer. Open to contributions by everybody.
Pro Git commands visibility
GitExtensions typically displays all commands that it carries out in a separate window. The user can also open the Gitcommand log (under Tools) and view the git commands as they interact with the program.
Pro SSH support
Instead of using HTTPS and authenticating every time they are pushing their code remotely, plenty of developers prefer to use SSH to communicate with the remote server and authenticate using secure key pairs.
Pro Powerful commit screen
Staging/unstaging files and/or lines of code, ammending, overriding commit's author, commit templates.
Pro Many advanced features made easier to use
Complex git commands such as resolving a rebase conflict or performing a subtree merge are made much easier by a helpful UI.
Pro Great UI
GitExtensions has a simple layout, all usual functions being available without navigation menus. The branching and merging are clear and easy to follow.
Pro Lightweight and fast
GitExtensions is a lightweight and fast application.
Pro Very good stash support
Easy to save, view & pop stashes.
Pro Easy to set up
Can either be set up as a shell extension, standalone tool of Visual Studio plugin, allowing developers to choose the way that suits their workflow best and is easier for them to get into.
Pro Easy to use
Can be used as a Visual Studio plugin for developers who use it as their IDE, or as a standalone tool. Both are easy to use even for users not very familiar with git.
Pro Submodule support
Powerful submodule support, also when working with multiple cloned SuperRepos.
Pro Responsiveness
Pro Useful plugins
Includes Gitflow, also has a delete obsolete branches feature which is very useful to get rid of those old branches that have already been merged. There are also other options to clean overall clutter in repositories.
Pro Built-in git-bash console
This makes running custom git commands quicker.
Pro Eases initial git configuration
The settings window on first run helps you set lots of required settings such as your commit email address.
Pro Simple global / local diff and merge support
Makes working with repos using different languages and support tools much easier.
Pro Allows easy setting up of scripts to enhance productivity
Pro Plugin API
There are several out-of-the-box plugins installed with standard setup. Additional behavior customization is possible with new plugins (written in C#).
Pro Integration with common tools like Jira or TeamCity
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 No side-by-side diff
There is no option to do side-by-side review of files. Creator(s) do not feel this is a desirable feature. While this is great software in almost all aspects, not giving the end-user a choice of side-by-side diff (inside GitExtensions) is a deal-breaker.
And no, using an external tool to do this is too much of a hassle, because of the amount of files to check in each change-set (in my case that are often 200 to 300 files).
Con Not truly cross-platform
GitExtensions is not truly cross-platform. It can run through mono on UNIX-based systems but this does not work as well as it does on Windows.
Con Missing tabs to have more repositories open at once
Con Doesn't offer " Repo Groups"
Repo groups (best done in smart git, Git Kraken's version is also decent) is an amazing time saving feature when you work with multiple repos on a daily basis. This is the only con!
Con UI does not render properly on Windows 10 x64
Con UI may feel cluttered with too much information
The sheer amount of information that the UI displays by default may feel overwhelming at times, if not outright confusing.
Con Linux version has no updates
If you want an updated version, you have to download the source and figure out how to build it yourself. Developers don't have any kind of documentation or faq about this process.