Re: How does team maintenace of python module works?
On Thursday, February 21, 2013 03:00:56 PM Charles Plessy wrote:
> Le Wed, Feb 20, 2013 at 11:02:15PM -0500, Scott Kitterman a écrit :
> > On Thursday, February 21, 2013 11:08:13 AM Chow Loong Jin wrote:
> > ...
> > > That argument applies to any VCS that you don't use on a daily basis.
> > > You
> > > use bzr on a daily basis and forget how to use git. I use git on a daily
> > > basis and forget how to use svn/bzr and have to relearn it any time
> > > someone
> > > forces me to use one of those. I don't think this is a valid reason for
> > > avoiding git.
> > ...
> > It is to a degree, but the learning curve for git is subtantially steeper
> > than for other VCS. I've learned CVS, SVN, BZR, and Git at one time or
> > another and there is no question in my mind which one, by a lot, is the
> > most complex to learn.
> Dear Scott,
> I undertand that learning Git after BZR is hard, because learning BZR after
> Git is equally painful. I think that the key difficulty is whether a
> system is learned first or second, not the system itself.
> This is where git-buildpackage is nice, as it re-implements the same user
> experience as with svn-buildpackage, and therefore provides some kind of
> upgrade path.
I disagree. Learning git is harder than all the others. It doesn't matter
what order you learn them in. If you look at the figures in point 10 of
http://steveko.wordpress.com/2012/02/24/10-things-i-hate-about-git/ (you can
largely substitute bzr for svn there and it won't get any more complex) and
tell me those are of equal complexity.
For all it's power, the git U/I is just inconsistent and counter intuitive.
If you use it routinely, you get so you remember it and it seems easy. If you
don't, you have to re-climb up the learning curve each time.