Practical Reasons To Choose Git Or Subversion?
markmcb writes "I develop Rails applications and recently followed my lemming herd and made the switch to Git after learning some of the practical advantages Git offers over Subversion. As I'm sure there are many die-hard Subversion fans in the Slashdot audience, I'm curious what your key reasons are for sticking with Subversion. If possible, I'd like reasons that apply to 'most of the time' as opposed to arguments based on obscure features that may get used only a few times ever."
Unless, of course, you're an IE user (ow, stop, the tomatos they burn!) and you get scripting errors on every Slashdot page, thereby making it impossible to tag, metamod, or participate in the new beta index article voting feature.
Comment removed based on user account deletion
cp(1) for merging? Are you nuts?
Larger projects with many developers require the ability to branch and merge large bodies of code. Larger projects with many developers require the ability to branch and merge large bodies of code.
Yes, and why is that?
It's because people have trouble forming teams and maintaining strong relationships in large groups. The cost of communication gets too high for humans to effectively maintain the shared understandings necessary to work smoothly together.
So again, branching is what you do when a group fails to work effectively as a team.
Personality conflicts may be the root-cause for you but is not the root for the majority of people that require such functionality. Simple fact is, branching and merging is required for complex software development.
I see. Please link to your data proving these are facts, because they look a lot like your personal opinions to me.