Things I hate about Git (2012)
stevebennett.me
Things I hate about Git (2012)
1–10 of 83 posts
Re: Things I hate about Git (2012)
#2Linus is not a UX guy, and it shows.
Re: Things I hate about Git (2012)
#3Linus is not a UX guy, and it shows.
However, he and many git users enamored of his style are perfectly willing to be condescending to anyone who points out the problems. Which itself is a problem.
Re: Things I hate about Git (2012)
#4Re: Things I hate about Git (2012)
#5Earlier quoted context omitted.
However, he and many git users enamored of his style are perfectly willing to be condescending to anyone who points out the problems. Which itself is a problem.
Is hg easier to use? Or any other DVCS not created by such a bad UX practitioner?
I was a major user of hg from 2007-2012, before I succumbed to network effects. The UX of hg was more intuitive for users coming from SVN and CVS.
Re: Things I hate about Git (2012)
#6"it's complicated": yes,it is. it's a product designed and built for people who deal with complex systems and information models on a daily basis; they're the equivalent of a professional pilot... not your feeble, senile grandmother. You wouldn't buy your feeble senile grandmother a 787, chuck her in with no training and simple expect her to fly to Bali, would you?
"I don't like it and here's a heap of examples which lead me to arrive at my preordained conclusion that it's completely broken": cool, you've found issues. If you can, fix them and share. If you can't or won't... well, there are other tools for doing version control and perhaps another might suit you better. If you have to work with people that use git, I'm sure there's some way you can generate patch sets and still get stuff done.
Re: Things I hate about Git (2012)
#7A lot of these complaints seem based on the fact that Git has features SVN doesn't and those features add complexity. Git really isn't that hard to learn. The trick is to take your time. If you try contributing to projects with complicated repos before you have a grasp on all the complexities, then yeah you're gonna have a bad time.
I could write a similar article about how FTP is so much easier to use than SVN and it would be equally silly.
That is not to say that Git isn't inconsistent and the docs are terrible, but there are good tutorials out there. If I were more helpful I'd have a link to one here but I'm on my phone.
Re: Things I hate about Git (2012)
#8I'm not anywhere near an expert with git, but I'm proficient enough to use it effectively with my normal workflow. I like git, but admittedly the bar was set really low by subversion.
This article raises some valid points, though. One that resonates most with me is that git exposes its entire model. I really wish there was a git-lite that just had the few basic commands that junior developers can grok and not fuck up so I wouldn't have to waste my time explaining the same stuff for the umpteenth time.
Re: Things I hate about Git (2012)
#9I've been using git for 7 years now. Never used anything else for version control (besides visual source safe which I try to forget).
Never felt the need or desire to try anything else.
Re: Things I hate about Git (2012)
#10Earlier quoted context omitted.
However, he and many git users enamored of his style are perfectly willing to be condescending to anyone who points out the problems. Which itself is a problem.
Is hg easier to use? Or any other DVCS not created by such a bad UX practitioner?
hg's command-line interface is far better organized, yes, at least in the sense that it appears to have been organized rather than organically slapped together and papered over with "well it'd make sense if only you understood more about it".
Blaming users for not understanding a bad interface is one of the classic mistakes.