When comparing Gogs vs Visual Studio Code, the Slant community recommends Gogs for most people. In the question“What are the best merge applications for Git?” Gogs is ranked 12th while Visual Studio Code is ranked 14th.
Ranked in these QuestionsQuestion Ranking
Pro Very light
Gogs is very light and has very low minimal requirements.
Pro Excellent performance and efficiency
The fact that it's written in Go means that it has excellent performance even with little resources (less RAM for example).
Pro Simple installation
The installation process is very simple, just a binary file that needs to be run on the directory where the user wants to install Gogs
Pro Open Source
Distributed under the MIT license.
Pro Cross-platform compatibility
Gogs is written in Go, this means that Gogs can be run anywhere that Go can compile. Be it Linux, Windows or OSX.
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 Embedded Git control
Visual Studio Code has integrated Git control, guaranteeing speed, data integrity, and support for distributed, non-linear workflows.
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
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 Libre/open source
Released under the MIT License.
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 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 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 Huge community behind it
The ease of getting assistance and finding tutorials is increasing as the community grows.
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 Python support
Excellent Python plugin, originally created by Don Jayamanne, now hired by Microsoft to extend and maintain the extension.
Pro JS typechecking
It leverages TypeScript compiler functionality to statically type check JS (type inference, JSDoc types) with
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 Good support for new Emmet syntax
Con Only one maintainer
The project is driven by only one maintainer. The development will stop if he for some reason stops supporting the project.
Con Can not make pull requests between branches of forked repositories
Con No third party provider support
Con Can't filter by a user to see all their commits in one place
I want to see a single user's entire history, but clicking a user's name only shows all users' history, not just the one I clicked.
Con Supports only git
Gogs supports only the Git management system.
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 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 Very bad auto import
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 Project search limits results
Because file search is so slow your results are limited in order to simulate a faster search.
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 Slow launch time
Than it's competitors, e.g. Sublime Text.
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 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.