How can we ensure Bazaar (bzr) remains active?

[Torsten Bronger]

Hallöchen!

Stephen J. Turnbull writes:

> Kevin Carrasco writes:
>
> [...]
>
>> is almost completely Python-based, was designed instead of built
>> (Git's slop of pieced together commands and scripts is not a
>> purpose-built design),
>
> No, but the underlying "the DAG's not the main thing, it's the
> only thing" design is the main reason git has a 10-try[5] lead in
> the market.

I don't know whether Kevin referred to this, but for me, "slop" in
Git is its grown rather than designed *UI*.  Its default values are
often poorly chosen, its subcommand structure is not consistent, and
its implicit behaviour tends to be surprising.  All in all, it is
unintuitive.

And this is the only aspect where bzr shines IMO.  I think that a
Bazaar-like access to Git's really powerful data model and to Git's
ecosystem is the only way to keep something Bazaarish alive on the
long run.

I realise that many parts of Bazaar could not survive this adaption.
But I consider those "dark corners".  To be honest, I didn't even
understand everything others said about Bazaar in this thread,
although I used Bazaar for years.  FWIW, for me, just a thin Bazaar
layer on top of Git would be marvellous.  Finally a "pull" wouldn't
automatically turn into a "merge" any more!  ;-)

Tschö,
Torsten.

-- 
Torsten Bronger    Jabber ID: torsten.bronger at jabber.rwth-aachen.de