Re: [weld-dev] [seam-dev] Mercurial vs GIT
On Nov 24, 2009, at 9:41 AM, Dan Allen wrote:
We all agreed to use git over svn, but to be honest, mercurial
wasn't considered. I've used both as well. But in my short exposure,
I really didn't see a difference. What makes git so attractive is
that github.com explains so well how to use it.
I supposed we could consider mercurcial if there was a nice out of
the box hosting option like github.com. If not, git will likely win
because of that.
I've done projects with both, and I think git, once you get over the
learning curve, is much easier to work with and get things done. With
mercurial, I always feel like I am fighting the system to make it
work. With git, the only struggle is learning the right commands, and
then once you do everything just works perfectly. I think the git
staging model is really nice, and I git stash can't be beat. If you
are working with a lot of branches or want to work on a lot of
separate issues at one time (develop features, fixes or support issues
separately in parallel) git is so much more pleasant. Mercurial isn't
bad by any means, but git just gets more things right, IMHO.
Attachments:
- attachment.html (text/html — 1.4 KB)