5 ms·

Why git is better than X

8 points by ptarjan 17y ago

philjackson 17y ago
Github - really? I just can't imagine Github being nearly as important to git adoption as some of those other points. It's a slow, clunky interface to a fast VCS.
davidw 17y ago
I more or less settled on git, but I think he's being glib with some of these points. For instance 'easy to use': many git commands require --funky 'options' -t -o get the desired results, whereas that's rarer with svn and systems that have taken that approach.
- dkersten 17y ago
  Also, I found that finding out what those funky options are is less than intuitive and not very well documented.
  - charlesmarshall 17y ago
    yeah, git documentation does suck .. but you can find most things on http://www-cs-students.stanford.edu/~blynn/gitmagic/ http://www-cs-students.stanford.edu/~blynn/gitmagic/ and example based things on http://gitready.com/ http://gitready.com/
- charlesmarshall 17y ago
  the majority of commands you use (clone, pull, push, branch, add) dont require many options at all .. -a -m -b .. Of course if you're doing something elaborate then you will get some random options like -soft or --before="yyyy-mm-dd hh:mm" .. those are generally things you can't do in svn .. edit: I forgot to mention that good guis like gitx do most of these things for you
  - davidw 17y ago
    > the majority of commands you use (clone, pull, push, branch, add) dont require many options at all .. -a -m -b .. It's not that bad, no, but with svn, I almost never had to use an option to the commands. My impression is that hg and bzr have followed svn's footsteps and have slightly nicer interfaces. That said, I'm relatively happy with git, but I view it as just a tool and not something to get too excited about:-)
  - InclinedPlane 17y ago
    This would be vastly improved if Git's documentation and help system wasn't so incomplete, out of date, convoluted, and messy. Git has an incredibly rich featureset, but the documentation often falls down in highlighting the 99% use cases so it ends up with a steeper learning curve than many other SCMs. I think this is one reason why Mercurial is so popular, at the scale of most development projects the advantages of Git over Mercurial are not terribly significant, but Mercurial has much, much better help and tutorials.
- etherealG 17y ago
  I'd rather have things more complex and have the ability, than simpler and not. By that argument we should all use horse carts instead of cars.
  - InclinedPlane 17y ago
    Cars are far easier to drive, and maintain, than a horse cart.
jeroen 17y ago
There is some interesting discussion here: http://news.ycombinator.com/item?id=381920 http://news.ycombinator.com/item?id=381920
tome 17y ago
Has darcs just disappeared off the radar? I'm using it for all my projects, though I'm not sharing wih anyone else, so I've never come under pressure to switch.
caddr 17y ago
My take from that chart is that if git was actually easy to use, it would be as good as svn. whoopee!

8 points by ptarjan 17y ago

Github - really? I just can't imagine Github being nearly as important to git adoption as some of those other points. It's a slow, clunky interface to a fast VCS.

davidw 17y ago

I more or less settled on git, but I think he's being glib with some of these points. For instance 'easy to use': many git commands require --funky 'options' -t -o get the desired results, whereas that's rarer with svn and systems that have taken that approach.

dkersten 17y ago
Also, I found that finding out what those funky options are is less than intuitive and not very well documented.
- charlesmarshall 17y ago
  yeah, git documentation does suck .. but you can find most things on http://www-cs-students.stanford.edu/~blynn/gitmagic/ http://www-cs-students.stanford.edu/~blynn/gitmagic/ and example based things on http://gitready.com/ http://gitready.com/
charlesmarshall 17y ago
the majority of commands you use (clone, pull, push, branch, add) dont require many options at all .. -a -m -b .. Of course if you're doing something elaborate then you will get some random options like -soft or --before="yyyy-mm-dd hh:mm" .. those are generally things you can't do in svn .. edit: I forgot to mention that good guis like gitx do most of these things for you
- davidw 17y ago
  > the majority of commands you use (clone, pull, push, branch, add) dont require many options at all .. -a -m -b .. It's not that bad, no, but with svn, I almost never had to use an option to the commands. My impression is that hg and bzr have followed svn's footsteps and have slightly nicer interfaces. That said, I'm relatively happy with git, but I view it as just a tool and not something to get too excited about:-)
- InclinedPlane 17y ago
  This would be vastly improved if Git's documentation and help system wasn't so incomplete, out of date, convoluted, and messy. Git has an incredibly rich featureset, but the documentation often falls down in highlighting the 99% use cases so it ends up with a steeper learning curve than many other SCMs. I think this is one reason why Mercurial is so popular, at the scale of most development projects the advantages of Git over Mercurial are not terribly significant, but Mercurial has much, much better help and tutorials.
etherealG 17y ago
I'd rather have things more complex and have the ability, than simpler and not. By that argument we should all use horse carts instead of cars.
- InclinedPlane 17y ago
  Cars are far easier to drive, and maintain, than a horse cart.

jeroen 17y ago

There is some interesting discussion here: http://news.ycombinator.com/item?id=381920 http://news.ycombinator.com/item?id=381920

tome 17y ago

Has darcs just disappeared off the radar? I'm using it for all my projects, though I'm not sharing wih anyone else, so I've never come under pressure to switch.

caddr 17y ago

My take from that chart is that if git was actually easy to use, it would be as good as svn. whoopee!