Hacker News new | comments | show | ask | jobs | submit login

I think you first have to ask why Microsoft is supporting git when Team Foundation is, itself, Microsoft's primary source control system.

The answer is most likely because people use git. Lots of people use git - particularly the crowd Microsoft is actively struggling to appeal to which is the entrepreneurial/startup crowd.

I've never used hg so I can't attest as to which is "better" but I really don't think that matters to most people. The only question is if it is "good enough" and git is.

The OP is simply saying that it seems odd that Microsoft would pour $20,000+ into Mercurial and then add git support to VS.


I'd bet this is simply a case of the right hand not knowing what the left hand is doing. I had no idea Microsoft were sponsoring Mercurial--even that seems odd, spending money on an open source competitor to a product they also make.

I think your analysis is spot on.

It's not like $20k is a lot to Microsoft.

It's more than the $0 it's given git.

Actually, MS has contributed significantly more than $20k worth of developer time to git / libgit2 over the past months, all open source GPL code

This only makes the $20K to Mercurial seem weirder, don't you think? It underscores my point that it's hard for large organizations to keep their official positions on things straight.

From a bigger-picture strategic sense, the Developer Division at Microsoft is concerned about making Microsoft a good platform for developers. Fundamentally, if developers want to use Mercurial on Windows or Git on Windows or TFS on Windows, we're happy. And - increasingly - we'll donate money or even developer time to help make this a good experience.

I've been an hg fan for a while and like it better (hg jives with my brain better and git occasionally throws weird problems at me) but quality wise I can't say there is much of a difference in my experience.

That said, I have never met a single other person who uses hg. Not at work or hackathons. Most have never even seen an hg repository and some haven't even heard of it. Git definitely has "won" this "war".

The problem is that large swathes of the Git community have been treating the whole DVCS scene almost in Hunger Games terms -- there can be only one winner, and all the others must die.

For what it's worth, I've heard quite a lot of anecdotal evidence that Git is pretty contentious among many teams that adopt it. Git adoption is often driven by an aggressive few, against the wishes of their colleagues who can be quite unhappy about it. Case in point: Git has more "hates" on amplicate.com than Subversion and TFS put together -- and "hates" outnumber "loves" by something in the region of four to one. (http://amplicate.com/hate/git)

(For reference, Git and TFS have roughly similar market share in the enterprise at the moment, and Subversion is about twice as widely used as either of them. Source: itjobswatch.co.uk)

I use hg for personal projects, but I agree that git has become almost a standard, and, as others mentioned, almost synonymous with the distributed version control systems. My feeling is the differences between git and hg are smaller than the advantages of switching from one to the other and reconditioning yourself to a slightly different work mode. (I guess I should have said "reconditioning myself".)

We use hg for all our stuff at work, and all the openjdk stuff uses it too.

I believe Mozilla uses hg for their source control.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact