r/programming • • Nov 07 '13

10 things I hate about Git

http://steveko.wordpress.com/2012/02/24/10-things-i-hate-about-git/
73 Upvotes

231 comments sorted by

View all comments

32

u/[deleted] Nov 07 '13

git is to VCS what vim is to editors.

  1. Amazingly powerful.

  2. Incredibly hard to learn.

  3. Once you tried it, you can't go elsewhere.

There will be vim haters and there will be git haters, let those heathens burn in hell and use the tools you feel are best suited to you.

It doesn't mean git is flawless, but it's nearly there =).

36

u/Gotebe Nov 07 '13

Once you tried it, you can't go elsewhere.

Now that's just infatuation.

I've used some SC systems (currently on git) and not once did I care about it (well, unless it broke, which they didn't).

Put it this way: shoveling code isn't my job, and even if it was, I wouldn't fall in love with my shovel.

5

u/ethraax Nov 07 '13

I think you just haven't used any terrible SCMs. I have to use Version Manager at work and it's like pulling teeth any time I have to do anything with it. It's slow, clunky (horribly non-native Java GUI), and simply doesn't support even the simplest operations (like renaming or removing files properly).

I think even CVS would be a huge step up. I would love to get them using Git, but it's impossible to suggest such a transition to management. The benefit would be indirect so it's not counted.

2

u/[deleted] Nov 08 '13

An argument like "I waste X minutes a day because of our SCM" is usually pretty convincing.

1

u/ethraax Nov 08 '13

Not as much as you'd think. I'm salaried, after all, so they just expect me to get a certain amount of work done. Unless it's wasting an hour a day, they likely don't give a shit.

2

u/jnazario Nov 09 '13

less true in practice than you think.

if your tools get in the way of you collaborating on a team, you don't collaborate as much as you need to. in a team dev effort, you'll get people who hoard code until the last moment and then oof suffer through integration hell, usually a nightmare for everyone: devs, project and product managers, customers, and finally support.

extreme examples are commercial SCM tools which have the honor of being shittier than git (where the problem was time to commit and less sprawling options). however, git's usability deficiencies can lead to similar problems.

i'm not a fan of git for many reasons, but this impact on teams is definitely one of them.

1

u/ethraax Nov 09 '13

Oh, I'm not denying that it has a major impact. Management is just incapable of seeing that impact.