←back to thread

Beej's Guide to Git

(beej.us)
1062 points mixto | 5 comments | 05 Feb 25 00:07 UTC | HN request time: 0.243s | source
Show context
scrapcode ◴[05 Feb 25 01:59 UTC] No.42942555[source]▶
I can't help but feel that Git has completely missed the forest through the trees that you can make a 30+ part guide explaining how to use it.
replies(6): >>42942641 #>>42942672 #>>42942768 #>>42943372 #>>42950299 #>>42954886 #
1. juped ◴[05 Feb 25 20:48 UTC] No.42954886[source]▶
Why are programmers so vehemently angry over the fact that a complex tool which does complex things to a complex data structure might have some complexity to it?
replies(3): >>42956182 #>>42960800 #>>42964309 #
2. zanellato19 ◴[05 Feb 25 22:25 UTC] No.42956182[source]▶
"I don't understand this complexity so this means it shouldn't exist"
replies(1): >>42999445 #
3. solidasparagus ◴[06 Feb 25 09:53 UTC] No.42960800[source]▶
It's the de facto tool for our industry. For the vast majority of cases, users bear the burden of that complexity without gaining much benefit. And (at least for me) it doesn't guarantee the one thing I need it to do - make sure I can never lose progress.
4. andrewflnr ◴[06 Feb 25 17:06 UTC] No.42964309[source]▶
The data structure isn't that complex. Most of the things we want to do to it aren't that complex. And yet... https://xkcd.com/1597
5. keithalewis ◴[10 Feb 25 12:21 UTC] No.42999445[source]▶
Linus wrote it, so there's got to be a pony in there somewhere. He's the first person in the world to figure out version control software. /s