From: Luis Lavena <luislavena@...>
Date: 2008-03-25T23:14:52+09:00
Subject: Re: Why git instead of mercurial?

On 25 mar, 10:43, "M. Edward (Ed) Borasky" <zn...@cesmail.net> wrote:
> John Wells wrote:
> > And God help me, I'd
> > rather program in Python and C than Perl and C any day. I assume this
> > is true for a lot of Ruby developers...while Ruby has its roots in
> > Perl, it's kinda like being a clean cut metrosexual with embarrassing
> > redneck parents you still humor and honor, but try not to bring to
> > social gatherings...
>
> Well ... I'd much rather program in Perl than Python. Why, you ask?
> Because I've been programming in Perl since about 1994 and I've never
> written even a single line of Python. I'm sure Python is a perfectly
> wonderful language, but the only thing that would "invite" me to learn
> it would be to get paid to write it.

I develop with Python a few years back, but not for that I'm using
Bazaar right now...

I'm using Bazaar instead of Git mostly because 'it just works' on
Windows and have a truly "official commitment" to support it.

Git, on the other hand, need not just some tweaking but also several
external tools to get it working...

Mercurial is similar to Bazaar (on the Windows support) Git-flavored.

Also the low-level and ugly UI git imposses in the workflow is a no no
for me, For those who like to be in control of everything, the
morphing working tress Git uses (one checkout for every branch you
want to do) I see it as something bad.

Example: I decide to branch the stable branch of one project and fix
some issues related to 'feature-x'

Worked on that branch and fired the spec tasks, which will rake 10
minutes to complete.

With git, I can't checkout another branch unless I do another clone.
With Bazaar, on the other hand, I can branch again, and again, and
again... and start hacking on other things right anyway, even the rake
tests didn't complete yet.

Again with UI, keep track of another head in a repo is a mess... git
track foo -b yyy what!?!? The UI is too complex...

If you want to contribute to a project and get something fixed, the
learning curve of the SCM is so steeped that you make contributors go
away...

Don't forget about "I just reverted long-sha-1-goes-here, since
another-long-sha-1-goes-here-too was broken"... :-P

I think is not a Perl/C vs Python/C issue, but Git is the new cool
toy.

Just my point of view,
--
Luis Lavena