Start networking and exchanging professional insights

Register now or log in to join your professional community.

Follow

Should the companies adopt the git, what are the pros and cons of going towards git?

Let's discuss about the GIT pros and cons based upon your experience's.

user-image
Question added by Mohammad Arif , Principal Engineer UI , NatWest Group
Date Posted: 2013/10/03
Mohammad Arif
by Mohammad Arif , Principal Engineer UI , NatWest Group

Have been using GIT on/off more then an year and found extremely good and powerful comparing with SVN, no doubt it requires bit of learning curve but once you all setup, you never look back to SVN, have used in last2-3 projects and doing the same in current one due to client codebase reside on GIT as a private repo using GIT Bash on windows.

Pros

  • Git is much faster than Subversion
  • Subversion allows you to check out just a subtree of a repository; Git requires you to clone the entire repository (including history) and create a working copy that mirrors at least a subset of the items under version control.
  • Git's repositories are much smaller than Subversions (for the Mozilla project,30x smaller), The Mozilla project's CVS repository is about3 GB; it's about12 GB in Subversion's fsfs format. In Git it's around 300 MB.
  • Git was designed to be fully distributed from the start, allowing each developer to have full local control
  • Git branches are simpler and less resource heavy than Subversion's
  • Git branches carry their entire history
  • Merging in Git does not require you to remember the revision you merged from (this benefit was obviated with the release of Subversion1.5)
  • Git provides better auditing of branch and merge events
  • Git's repo file formats are simple, so repair is easy and corruption is rare.
  • Backing up Subversion repositories centrally is potentially simpler - since you can choose to distributed folders within a repo in git
  • Git repository clones act as full repository backups
  •  

Cons

  • Subversion's UI is more mature than Git's
  • Walking through versions is simpler in Subversion because it uses sequential revision numbers (1,2,3,..); Git uses unpredictable SHA-1 hashes. Walking backwards in Git is easy using the "^" syntax, but there is no easy way to walk forward.

Do you need help in adding the right keywords to your CV? Let our CV writing experts help you.