Re:Distributed Version Control is here to stay, baby
by axod on Thursday March 18, 2010 @10:25AM
(#1201363)
In what way easier?
A: Create separate branches, manage merging/updating unrelated changesets.
B: Create 2 implementations of something in code, and manage nothing.
I guess it depends on how easy it is to isolate the part you want to create 2 implementations of, so it may depend on what language you're using as well as how you architected things.
Branching+Merging just seems like something extra I have to do, manage, and remember. Like filing. And I still can't see what benefit it gives for many cases.
But that's fine I think... I just don't get it. Maybe I'm too old ;)
A: Create separate branches, manage merging/updating unrelated changesets.
B: Create 2 implementations of something in code, and manage nothing.
I guess it depends on how easy it is to isolate the part you want to create 2 implementations of, so it may depend on what language you're using as well as how you architected things.
Branching+Merging just seems like something extra I have to do, manage, and remember. Like filing. And I still can't see what benefit it gives for many cases.
But that's fine I think... I just don't get it. Maybe I'm too old ;)