That said hg is the better choice for big software shops IMO, because of the lower training cost and because they probably won't use github anyway.
That said hg is the better choice for big software shops IMO, because of the lower training cost and because they probably won't use github anyway.
Considering more people know git I would assume the training cost for hg is higher.
And yet I have noticed that people find merging and branching much easier than in mercurial. Few people understand the implications of named branches in hg.
That's the first time I've heard this opinion - do you know what kind of complaints people have?
In my experience, it's much easier to say 'When you start work on an issue, start a branch called 'issue-XXX', then once you're done we will merge it into the default branch'. I've never seen much confusion in response to that.
In contrast, git branches symlink to a different ref, whenever you commit to it.
A git tag could be called bookmark intuitively.