What's your PotentialMulti-Site ROI?
The ForresterWave™: Web ContentManagement Systems,Q1 2015
We're HiringFeatured Position: Account Executive Apply Now
In my opinion, Git is too clever for it's own good. I
acknowledge it's power, but I don't feel like having to earn
a PhD in Git just to use it. I'm over the complexity and now
yearn for the safety and simplicity of Subversion. I found this page
because, after 3 years away from svn, I'm curious to see if the
merging power is improved to Git-like levels. On the assumption that
it is, I'd encourage any small or medium team to pick Subversion
over Git if you aren't anal about avoiding a central repository.
(But if that was the case, explain why teams so often use GitHub...
(ok, you don't really have to explain))
If you don't want to employ a full-time merge master, or you
are afraid of your dev team being crippled if this magician leaves,
try Subversion first. Sure, Git will give the repository master more
power, but it'll annoy, confuse and scare the hell out of the
regulars, or they'll just pretend they like it...
I for one am fed up with spending a day at a time fixing a mess
just because I haven't put a massive investment into studying Git
inside and out. I want simplicity! Adding simplicity is always a good
step for any system. Git desperately needs a good dose...
Sigh, think I have to study Git in depth even though I
shouldn't have to; there's no avoiding it. Maybe in 6 months
I'll come back and explain how simple it is, but then again,
Cheers and peace-out homies.
More information about text formats