Comments on: The Power of Git, Part 2 http://kurt.karmalab.org/2008/02/19/the-power-of-git-part-2/ Schrade.Blog Fri, 09 Jul 2010 06:07:11 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Maxim Kulkin http://kurt.karmalab.org/2008/02/19/the-power-of-git-part-2/comment-page-1/#comment-199 Maxim Kulkin Wed, 30 Nov -0001 00:00:00 +0000 urn:uuid:{a.guid}#comment-199 It's funny to see how people discover DSCM (distributed source code management) systems just because some guy in Rails community noticed it. I was using Darcs (yet another DSCM) for 2 years. And this bugs me, because everybody think that git is the only one that does this. It’s funny to see how people discover DSCM (distributed source code management) systems just because some guy in Rails community noticed it.

I was using Darcs (yet another DSCM) for 2 years. And this bugs me, because everybody think that git is the only one that does this.

]]> By: David S. http://kurt.karmalab.org/2008/02/19/the-power-of-git-part-2/comment-page-1/#comment-200 David S. Wed, 30 Nov -0001 00:00:00 +0000 urn:uuid:{a.guid}#comment-200 I did not know Linus Torvalds was involved with Rails! I did not know Linus Torvalds was involved with Rails!

]]> By: Michael http://kurt.karmalab.org/2008/02/19/the-power-of-git-part-2/comment-page-1/#comment-201 Michael Wed, 30 Nov -0001 00:00:00 +0000 urn:uuid:{a.guid}#comment-201 Maxim, it's not "funny" or bothersome for any reason whatsoever. It's just generally awesome that people are discovering it. Period. Really, just be happy that bloggers like Kurt are promoting distributed source control and move on. Maxim, it’s not “funny” or bothersome for any reason whatsoever. It’s just generally awesome that people are discovering it. Period. Really, just be happy that bloggers like Kurt are promoting distributed source control and move on.

]]> By: eddie http://kurt.karmalab.org/2008/02/19/the-power-of-git-part-2/comment-page-1/#comment-202 eddie Wed, 30 Nov -0001 00:00:00 +0000 urn:uuid:{a.guid}#comment-202 Wow, if Torvalds is involved with Rails, then the scalability problems are going to go soon. Great. /LOL> Wow, if Torvalds is involved with Rails, then the scalability problems are going to go soon. Great.

/LOL>

]]> By: nn@example.org http://kurt.karmalab.org/2008/02/19/the-power-of-git-part-2/comment-page-1/#comment-203 nn@example.org Wed, 30 Nov -0001 00:00:00 +0000 urn:uuid:{a.guid}#comment-203 If SVN is the core and everyone is using git around it, for a while it will resemble a cork surrounded by a bunch of swiss army pocket knives. If SVN is the core and everyone is using git around it, for a while it will resemble a cork surrounded by a bunch of swiss army pocket knives.

]]> By: Maxim Kulkin http://kurt.karmalab.org/2008/02/19/the-power-of-git-part-2/comment-page-1/#comment-204 Maxim Kulkin Wed, 30 Nov -0001 00:00:00 +0000 urn:uuid:{a.guid}#comment-204 Heh, that's how rumors are born. I didn't say it was Linus. Linus wrote git long time before it was adopted by Rails-ians. And there were other DSCMs before Linus'. I'm sure, lots of Rails-ians think that Git was invented by some fellow Rails guy, because he was sick of some "code ghetto". But the most bad think I think is that Git is advertised to newcomers as _the_only_way_ to do some code management stuff (e.g. starting new project). And newcomers are forced to learn just another "cool" tool that "does some great magick" without even understanding why's and how's. Heh, that’s how rumors are born. I didn’t say it was Linus. Linus wrote git long time before it was adopted by Rails-ians. And there were other DSCMs before Linus’.

I’m sure, lots of Rails-ians think that Git was invented by some fellow Rails guy, because he was sick of some “code ghetto”.

But the most bad think I think is that Git is advertised to newcomers as _the_only_way_ to do some code management stuff (e.g. starting new project). And newcomers are forced to learn just another “cool” tool that “does some great magick” without even understanding why’s and how’s.

]]> By: Kurt Schrader http://kurt.karmalab.org/2008/02/19/the-power-of-git-part-2/comment-page-1/#comment-205 Kurt Schrader Wed, 30 Nov -0001 00:00:00 +0000 urn:uuid:{a.guid}#comment-205 Maxim: Are you trying to make a point about something? 1. I have a Darcs repo from several years ago with some web crawler code in it, written in Haskell and Ruby. I don't see how that's relevant to this, except to point out that Darcs isn't as nice as git. 2. If you look at the [link in the post](http://utsl.gen.nz/talks/git-svn/intro.html#sux), code ghetto is defined as: >The 'Ghetto' development model >This is where you send new features into the ghetto so that they can 'battle it out'. The last features standing get re-integrated into another branch known as the trailer park to try to find a new life for themselves. >Note that ghetto is frequently called trunk, and the trailer park something like releng. The 'hood is frequently mis-spelled "head". It has nothing to do with Rails. 3. In fact, I didn't mention Rails at all in the post. Maxim:

Are you trying to make a point about something?

1. I have a Darcs repo from several years ago with some web crawler code in it, written in Haskell and Ruby. I don’t see how that’s relevant to this, except to point out that Darcs isn’t as nice as git.

2. If you look at the [link in the post](http://utsl.gen.nz/talks/git-svn/intro.html#sux), code ghetto is defined as:

>The ‘Ghetto’ development model

>This is where you send new features into the ghetto so that they can ‘battle it out’. The last features standing get re-integrated into another branch known as the trailer park to try to find a new life for themselves.

>Note that ghetto is frequently called trunk, and the trailer park something like releng. The ‘hood is frequently mis-spelled “head”.

It has nothing to do with Rails.

3. In fact, I didn’t mention Rails at all in the post.

]]> By: bwtaylor http://kurt.karmalab.org/2008/02/19/the-power-of-git-part-2/comment-page-1/#comment-206 bwtaylor Wed, 30 Nov -0001 00:00:00 +0000 urn:uuid:{a.guid}#comment-206 Git has three problems that I think make it difficult to switch to in corporate dev shops... 1) No windows support (and cygwin doesn't count). This makes it a non-starter in many enterprise settings. Mercurial is the obvious alternative for you if you have windows people on your team. 2) The command set is large and complex. It deviates needlessly from its predecessors cvs and svn. This creates a bigger activation barrier to adopting it in a team setting. Mercurial is much better in this regard. 3) Unfortunately push is not a symmetric version of pull and this is confusing. If you follow the advice avoid push to a "non-bare" repository then you aren't truly a peer-to-peer system as you have to be aware of which repositories are bare and which might have working copies checkout out. This sucks. I think 1 and 3 are solveable. I think 2 is permanent. Git has three problems that I think make it difficult to switch to in corporate dev shops…

1) No windows support (and cygwin doesn’t count). This makes it a non-starter in many enterprise settings. Mercurial is the obvious alternative for you if you have windows people on your team.

2) The command set is large and complex. It deviates needlessly from its predecessors cvs and svn. This creates a bigger activation barrier to adopting it in a team setting. Mercurial is much better in this regard.

3) Unfortunately push is not a symmetric version of pull and this is confusing. If you follow the advice avoid push to a “non-bare” repository then you aren’t truly a peer-to-peer system as you have to be aware of which repositories are bare and which might have working copies checkout out. This sucks.

I think 1 and 3 are solveable. I think 2 is permanent.

]]> By: Surewish http://kurt.karmalab.org/2008/02/19/the-power-of-git-part-2/comment-page-1/#comment-207 Surewish Wed, 30 Nov -0001 00:00:00 +0000 urn:uuid:{a.guid}#comment-207 Boy do I wish I was hip enough to give a shit about any of this. (regarding comments) Nice blog though Boy do I wish I was hip enough to give a shit about any of this.
(regarding comments)

Nice blog though

]]> By: bjwilson http://kurt.karmalab.org/2008/02/19/the-power-of-git-part-2/comment-page-1/#comment-208 bjwilson Wed, 30 Nov -0001 00:00:00 +0000 urn:uuid:{a.guid}#comment-208 Typical Rubyist tries to claim he was on the bandwagon before it was cool. Grow up. Darcs does not scale darcs cannot handle big files. Darcs has an exponential time merge resolution which just kills it. Haskell makes darcs chew through memory like it was free and large changes can go over 32bit boundaries in memory usage. All in all darcs had a good UI but failed due to implementation problems. Typical Rubyist tries to claim he was on the bandwagon before it was cool. Grow up. Darcs does not scale darcs cannot handle big files. Darcs has an exponential time merge resolution which just kills it. Haskell makes darcs chew through memory like it was free and large changes can go over 32bit boundaries in memory usage. All in all darcs had a good UI but failed due to implementation problems.

]]>