Benchmark: Git 1.6.3.3, Hg 1.3.1, Bzr 1.17

[Stephen J. Turnbull]

David Ingamells writes:
 > Andrew Cowie wrote:

 > > And meanwhile if you're working [like this == like me] ... [I
 > > recommend] http://java-gnome.sourceforge.net/4.0/HACKING.html 
 > > but only rarely do people actually know of or follow the recipe (let
 > > alone following it all the way to having a switched Eclipse project).

 > I don't see why this must be *the* "proper" way of working. Certainly 

He didn't say *the* in a global sense.  He said it was best practice
in his context.

 > for the large number of bzr users who aren't using eclipse or any
 > other IDE that is similarly so restrictive about how you must set
 > up a project.
 > 
 > For users working only on a local (and fast) network [I would do it
 > differently, maybe more simply].

That is exactly the problem Andrew is pointing up.  Bazaar is
*flexible* -- you can bend it into any shape you need -- but it is
*not adaptive* -- you have to do the bending yourself.  It does not
shape itself to the task in front of you.

It's clear from the things that people like Robert and Aaron say about
how they use bzr that in fact you can do almost anything any VCS can
do from almost any configuration of repository, branch, and formats.
But this is not discoverable, it requires extensive familiarity with
both command options and VC theory (and sometimes maybe even bzr
source), and setting up an initial workflow is fraught with options
and settable defaults that later you forget how to override, or may be
difficult to change "on the fly" in the middle of a project.

 > 3) I am often working on several distinct tasks in parallel, either on 
 > the same project or on distinct projects. Using switch in this scenario 
 > could get very confusing!

There may be *better* ways of doing it in Bazaar, but it shouldn't be
something to avoid.