[Adium-devl] Version Control - To change or not to change? THAT is the question!

Augie Fackler lists at durin42.com
Wed Jan 2 07:29:47 UTC 2008


> The Mozilla project did a sample conversion of their 10 year, 240,000
> commit repository: a single checkout was 350 MB, CVS stored the
> history in 3 GB, SVN in 12 GB, and Git in 300 MB. Yes, megabytes. The
> entire history was stored in less space than a single full version of
> the source tree.

This brings up a point I've never seen directly asked (maybe I just  
chill with the wrong VCS crowd):
Doesn't using this kind of insane compression make accessing the  
history insanely slow?

>> 3.0 My Conclusion
>> Sometimes the choice of development tools borders on a "religious  
>> war", and
>> each person involved often holds deeply rooted beliefs that are  
>> difficult to
>> change.  I myself resisted the switch from CVS to SVN for well over  
>> a year
>> until I changed, and was eventually glad that I did.
>>
>> However, as I look at the maturity and features of the current  
>> state of DVCS
>> systems.  I find myself weighing the pro's and con's, but still  
>> find myself
>> entrenched in the "It ain't broke, so don't fix it" camp for the  
>> Adium
>> project.
>
> My summation: "It *is* broke, you just don't realise it."

I don't think assuming it's broken is safe - honestly, merging  
*works*, just not as cleanly as we'd like. That said, DVCS does offer  
some (reasonably, IMO) compelling features that are nice-to-haves, not  
"missing features" that imply brokenness in Subversion.

Peace,
Augie





More information about the devel mailing list