I can't believe anyone could come up with an information model and user interface so convoluted and incoherent. Just one example of many such vomit-inducing ones:
to setup a remote tracking branch of "remotes/origin/master" you'd do:
git fetch origin master:remotes/origin/master
but to delete the same thing you'd do:
git branch -rd origin/master
see the autism there? the two commands do not specify the same identity for the same object. I could go on and on and maybe even put up a blog post but I'm not one of those "hacker" news faggots.
An ``autistic'' interface would be impossibly symmetric. Or is autism the new retard?
Name:
Anonymous2012-08-07 16:31
>>4 that's why he added asymmetric in front of the autism nigga. it's like the unstoppable idiocy of Linus meets the unmovable gayness of Junio. Nigga you told.
I wish those so-called ``hackers'' (Eric S. Raymond, Linus Torvalds, Larry Wall, Theo de Raadt, etc.) would recognise that the Unix philosophy and the bazaar model of development are just elaborate jokes.
Name:
Anonymous2012-08-07 16:41
If darcs supports cheap branching (no, making a copy of the whole repo isn't branching) then I'd be all over it. git is quite possible Linus' greatest prank.
Name:
Anonymous2012-08-07 16:45
It's the spaghetti with meatballs of versioning. The meatballs of course is, Linus's balls.
Another git fuckery is the git config command. Notice that some config keys are camelCase and some are smashedlowercase. How is this coherent in any way? And I can even bet the way they handle it is by literally patching up the .git/config file, probably by using some vile perl script, rather than serializing/unserializing a coherent model and using validation. For example, I can get that file to have the following contents not by editing it directly, but by using the git-config command:
...
[merge]
[merge]
defaultsToUpstream = true
...
There are a couple of WTF in that snippet: a) how is it possible that git-config can have two "merge" config sections? and b) defaultsToUpstream is not even a valid configuration variable.
Obviously no configuration file schema validation was made. git confirmed for amateurish programming at best. a toy project indeed.
Name:
Anonymous2012-08-07 18:03
>>11
Fine, then suggest a secure (therefore open-source and authenticated via public key cryptography), efficient, non-WTF distributed revision control system.
Just for fun, here's the exact commands to produce >>11 :
git config merge.defaultsToUpstream true
git config --unset merge.defaultsToUpstream
git config merge.defaultsToUpstream true
Name:
Anonymous2012-08-07 18:23
git is like English. It's seemingly illogical and incoherent.
Name:
Anonymous2012-08-07 18:33
>>13
Does hg have a GUI, similarly to how git has gitk?
>>17 I know right, I need it to handle at least 9000 req/s for my repo server.
Name:
Anonymous2012-08-07 19:19
>>11 The funny thing is if you go on irc.freenode.net#git and say "git confirmed for amateurish programming at best" you'll undeniable get kicked out, despite the truth in what you're saying. git was and still is an amateur project by the very definition of the word.
amateur |ˈamətər; -ˌtər; -ˌ ch oŏr; - ch ər|
noun
a person who engages in a pursuit, esp. a sport, on an unpaid basis.
The fanboi faggotry is strong in this project.
Whenever I work with git it's always decapitating itself. Detached head? So now that I've checked out a remote branch, I have the head of my penis hanging on my just a urethra, basically. Detached head my ass. Just checkout the damn branch and let me know I can't push to it, but don't chop off my dicktip.