Probably the single biggest reason, aside from it&#x27;s easier to use than git&#x27;s CLI, is that it has sub-modules that work exactly like files do in a repository.  No extra options, just clone&#x2F;pull&#x2F;push&#x2F;commit&#x2F;etc.  Full on distributed workflow.<p>BitKeeper itself is a collection of repositories.  Download an install image, install, and clone it:<p><pre><code>    $ bk clone http:&#x2F;&#x2F;bkbits.net&#x2F;u&#x2F;bk&#x2F;bugfix
    $ cd bugfix
    $ bk here
    PRODUCT
    default
    $ bk comps -m
    .&#x2F;src&#x2F;gui&#x2F;tcltk&#x2F;bwidget
    .&#x2F;src&#x2F;gui&#x2F;tcltk&#x2F;tcl
    .&#x2F;src&#x2F;gui&#x2F;tcltk&#x2F;tk
    .&#x2F;src&#x2F;gui&#x2F;tcltk&#x2F;tkcon
    .&#x2F;src&#x2F;gui&#x2F;tcltk&#x2F;tktable
    .&#x2F;src&#x2F;gui&#x2F;tcltk&#x2F;tktreectrl
    .&#x2F;src&#x2F;win32&#x2F;dll&#x2F;scc
    .&#x2F;src&#x2F;win32&#x2F;dll&#x2F;shellx
    .&#x2F;src&#x2F;win32&#x2F;dll&#x2F;shellx&#x2F;src
    .&#x2F;src&#x2F;win32&#x2F;msys
    .&#x2F;src&#x2F;win32&#x2F;vss2bk
</code></pre>
which shows that what we clone by default doesn&#x27;t include all that other crud (we cache the build result from that and populate it as needed to do builds).<p>Play with it, it&#x27;s very different from Git, the subrepo binding is just like file bindings.  Everything works together and obeys the same timeline.