version control - Why Kiln is based on Mercurial, and not other (D)VCS

Question

What were the reason for chosing Mercurial as a basis of FogCreek Kiln, a source control management system with tightly integrated code review, and FogBugz integration?

Why Mercurial, and not other (distributed) version control system, like Bazaar, Git or Monotone, or creating own version control system like Fossil (distributed software configuration management, including bug tracking and wiki) did?

What were features that make FogCreek choose Mercurial as Kiln engine?

Answer 1

Here's an answer from one of the Kiln developers.

• It provides real branching.
• It's easy to use.
• Windows support is very good.
• It's fast.
• It's powerful.
• It's easily extensible.

Check out the full details here. They explained themselves quite thoroughly.