Git vs Sonatype Nexus: What are the differences?
Git: Fast, scalable, distributed revision control system. Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency; Sonatype Nexus: The world's best way to organize, store, and distribute software components. Deliver better, safer software even faster with software supply chain automation.
Git and Sonatype Nexus are primarily classified as "Version Control System" and "Java Build" tools respectively.
Git and Sonatype Nexus are both open source tools. It seems that Git with 28.2K GitHub stars and 16.3K forks on GitHub has more adoption than Sonatype Nexus with 527 GitHub stars and 237 GitHub forks.
Netflix, reddit, and Lyft are some of the popular companies that use Git, whereas Sonatype Nexus is used by MIT, Auto Trader, and Smart.Biz. Git has a broader approval, being mentioned in 3934 company stacks & 4790 developers stacks; compared to Sonatype Nexus, which is listed in 49 company stacks and 16 developer stacks.
What is Git?
What is Sonatype Nexus?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Sonatype Nexus?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Sonatype Nexus?
Sign up to add, upvote and see more consMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
I use Git instead of SVN (Subversion) because it allows us to scale our development team. At any given time, the Zulip open source project has hundreds of open pull requests from tens of contributors, each in various stages of the pipeline. Git's workflow makes it very easy to context switch between different feature branches.
I've been excited about Git ever since it got a built-in UI. It's the perfect combination of a really solid, simple data model, which allows an experienced user to predict precisely what a Git subcommand will do, often without needing to read the documentation (see the slides linked from the attached article for details). Most important to me as the lead developer of a large open source project (Zulip) is that it makes it possible to build a really clean, clear development history that I regularly use to understand details of our code history that are critical to making correct changes.
And it performs really, really well. In 2014, I managed Dropbox's migration from Mercurial to Git. And just switching tools made just about every common operation (
git commit etc.) 2-10x faster than with Mercurial. It makes sense if you think about it, since Git was designed to perform well with Linux, one of the largest open source projects out there, but it was still a huge productivity increase that we got basically for free.
If you're learning Git, I highly recommend reading the other sections of Zulip's Git Guide; we get a lot of positive feedback from developers on it being a useful resource even for their projects unrelated to Zulip.
I use Visual Studio Code because at this time is a mature software and I can do practically everything using it.
It's free and open source: The project is hosted on GitHub and it’s free to download, fork, modify and contribute to the project.
Multi-platform: You can download binaries for different platforms, included Windows (x64), MacOS and Linux (
LightWeight: It runs smoothly in different devices. It has an average memory and CPU usage. Starts almost immediately and it’s very stable.
.properties, XML and JSON files.
Integrated tools: Includes an integrated terminal, debugger, problem list and console output inspector. The project navigator sidebar is simple and powerful: you can manage your files and folders with ease. The command palette helps you find commands by text. The search widget has a powerful auto-complete feature to search and find your files.
Extensible and configurable: There are many extensions available for every language supported, including syntax highlighters, IntelliSense and code completion, and debuggers. There are also extension to manage application configuration and architecture like Docker and Jenkins.
Integrated with Git: You can visually manage your project repositories, pull, commit and push your changes, and easy conflict resolution.( there is support for SVN (Subversion) users by plugin)
been an avid git user for over 6 years. was a little hard to grasp coming from the world of perforce but once it hit me that it was just a glorified patch manager everything fell into place. mainly use the command line interface, most ui's feel bulky and weak.
Git has rendered itself to be an integral part of all development at JustChunks. We heavily rely on Git as our version-control-system of choice and use branches, tags and decentralized-development to achieve our software-management-goals.
I use Git because there is nothing else that seems better for backup and working with other developers. However, the learning curve is high and there are times when non-developers must also know how to use git.
the next generation of version control, all others follow older outdated models. Open Source, no fees to use. Can hoist up your own internal server. Can live on a thumb drive. Developers can share from any OS.
Git ist ein essentieller Bestandteil unserer Entwicklungsteams. Sei es zur Versionskontrolle, Backupen von Code, dem gemeinsamen arbeiten an Projekten. Durch Git Flow haben wir eine effektive Arbeitsweise.