How Do You Control Your Source Code?

[eluser]jedd[/eluser]
Hi n0xie,

You appear to be contradicting yourself a bit here. You assert that git is difficult to grasp for most people who are used to other version control systems, and at the same time you are suggesting that Brian learns a different version control system before trying to use git. Sounds like you're trying to make it extra hard for the poor chap!

I disagree about the steep learning curve with git. The two links I posted in that other thread would get you running - and cover pretty much all of Brian's requirements alluded to above - in under an hour.

The 'whole world uses it so it must be good' theory isn't up to your usually high standards, either. If that was a sound principle, we'd all be lining up with our thousand US$ to buy our own copies of Fista + Office. And we'd all be using Cake / Zend. (Though in your defence, we'd be spending time learning those so that it'd be more confusing for us when we came over to CI.

Version control systems are something that, like a handful of other typically large / collaborative software types, are very hard to change mid-project. The linux kernel did it - mostly out of sheer bloody mindedness and a complete lack of viable alternatives I concede - but nonetheless it's a massive undertaking to swap over to a different vcs. Consequently most of the Whole World is using svn purely because svn has been around longer than their project, and at the time they started svn wasn't as sucky as cvs. Not a hugely compelling reason to jump on the subversion bandwagon for any new project, IMO.