[rscale]

I could be wrong, but I don't think the git/mercurial integration is the big point of Kiln.

Rather, harmony seems like an interesting side effect generated when Fog Creek built some swank tools for mercurial-based corporate developers, and git won the war while they were doing so.

Most of the value I see in Kiln is in the activity filters, the notifications, the code review tools, the ACLs, and FogBugz integration. Git/Mercurial interoperability is just a cute feature.

[diminoten]

It opens doors which were, until now, closed to the Fog Creek people. I bet this was said a ton:

"I like their tools, but does it support git?"

Now, the answer is: "Yes, it does."

I'd say that's a tad more than a "cute feature".

[jwr]

As someone who said exactly that and pays for FogBugz, but uses GitHub: now I read about what they did and think "why would they do that? It's a horribly complicated technical problem, I can't be sure they got it right, I'll stick to GitHub".

So, still no money from me, unfortunately.

[erikvanzijst]

> I can't be sure they got it right, I'll stick to GitHub

I guess you could just not use the feature and only use git clients. Who cares if the redundant hg clone they keep on their end gets out of sync.

[rscale]

I absolutely agree that Fog Creek needed to support Git, but I don't think Harmony sells meaningfully more than Git-only + hg-only would've. That's why I refer to it as a cute feature.

Fog Creek's emphasis on how they achieved git support steered the discussion to be about the value of git/hg interoperability, rather than the value of Kiln for corporate developers. And it seems like the consensus is that git/hg interoperability is, at best, a nice-to-have.

[mhp]

I think that's a fair criticism. Point taken.