News for hackers. Stuff that matters.

A comment on Announcing Kiln Harmony: the Future of DVCS. Parent comment

Re:Announcing Kiln Harmony: the Future of DVCS by diminoten on Tuesday March 12, 2013 @03:31PM (#5364290)
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".

[ Parent | on HN ]
Re:Announcing Kiln Harmony: the Future of DVCS by jwr on Wednesday March 13, 2013 @03:29AM (#5367281)
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.

[ Parent | on HN ]
Re:Announcing Kiln Harmony: the Future of DVCS by erikvanzijst on Wednesday March 13, 2013 @03:21PM (#5370519)
> 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.

[ Parent | on HN ]
Re:Announcing Kiln Harmony: the Future of DVCS by rscale on Tuesday March 12, 2013 @03:48PM (#5364397)
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.

[ Parent | on HN ]
Re:Announcing Kiln Harmony: the Future of DVCS by mhp on Tuesday March 12, 2013 @03:51PM (#5364416)
I think that's a fair criticism. Point taken.
[ Parent | on HN ]