When comparing Visual Studio vs gitk, the Slant community recommends Visual Studio for most people. In the question“What are the best Git clients for Windows?” Visual Studio is ranked 16th while gitk is ranked 26th. The most important reason people chose Visual Studio is:
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.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
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
Pro Visibly more compact overview output than many other options
When using gitk to scan a long list of changes, the user is able to see more of the list without pagination, as there is no huge buffer of whitespace between each entry.
Pro Fast
Since it's pretty minimalistic and does not contain a lot of features (for example, it can't commit), it's quite fast.
Pro Free
Gitk is a free and open source tool. It forms part of the official git suite.
Pro Comes with Git
Gitk is a part of the git package, so no additional application is necessary: it is developed right alongside git itself.
Pro Easy to use
Cons
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.
Con Cannot commit
The user needs to use a different Git client (GUI or otherwise) to commit changes.
Con Does not automatically update
The user must press F5 to refresh the view as there is no automatic update available.