4 ms·
" But I also know the pain of merging all too well - a benefit that I hadn't really seen explained as persuasively before." FWIW, try to give a few DVCS tools
by jamesbritt 17y ago
" But I also know the pain of merging all too well - a benefit that I hadn't really seen explained as persuasively before."
FWIW, try to give a few DVCS tools a shot before settling on one.
I was a big hg fan, and really didn't care to switch when my coworkers ganged up on me and decided that git was a better tool, but I think they were right.
The git command line leaves much t be desired; hg was far more intuitive. But I would occasionally have merging issues with hg that were just too annoying (lost or missing file changes, for example) that I haven't had with git.
But that's anecdotal, and I'm sure (if you follow enough dvcs flame/troll threads :)) you'll hear other stories about other tools. The upshot is to try a few to see which works best for your particular needs.
- vog 17y agoI've had the opposite experience: There are scenarios where Git reverts some changes unexpectedly and almost silently, if you don't take care. In contrast, Mercurial's strict "every merge is an explicit commit" principle saved me from a lot of problems. Regarding the command line interface: Darcs has still the best one. Well, Darcs has some performance issues, but its interactive dialog-based command line interface is outstanding. It is years old, but neither Mecurial nor Git come even close to it. So if you have a small project or a fast computer, you should definitely have a look at Darcs in addition to Mercurial and Git.