r/programming • • Jun 19 '14

Reinventing GIT interface

http://tonsky.me/blog/reinventing-git-interface/
221 Upvotes

325 comments sorted by

View all comments

Show parent comments

18

u/abolishcopyright Jun 19 '14

I'm not "stumped" but learning its interface is a time sink, and my time is valuable. I've been waiting for someone to write a smarter interface wrapper around it.

2

u/cpbills Jun 19 '14

The time saved in learning how to use git effectively more than makes up for the time spent learning how to use it.

In fact, you could probably replace 'git' in that sentence with ANY good tool.

-15

u/[deleted] Jun 19 '14

It's just not that hard to use though. If you're a competent software developer and this is that big of a deal you might want to do some thinking about how competent you are.

12

u/[deleted] Jun 19 '14

Maybe you should take a hint from your username and stop calling other people incompetent and stupid. It makes you look like a major douche.

-7

u/[deleted] Jun 19 '14

I am behaving. You're wasting your employers money if you're drawing salary as a software developer and you can't learn to use Git.

It's just not that hard to use. I taught myself the gist of doing commits/branches/etc over a weekend while playing with my [then] baby daughter.

I learned more of the finesse of doing rebases/HEAD movements over time but simply being able to work in Git took less than a week to learn.

2

u/immibis Jun 19 '14

You're wasting your employer's money if you're drawing salary as a software developer and you can't learn to use node.js and MongoDB. So go! Do it now! If you can't use node.js and MongoDB you're a terrible software developer who should be fired immediately!

/s

0

u/[deleted] Jun 20 '14

Except this was a thread about people already using it for work. If my work required me to use node.js I'd go out and learn it.

1

u/immibis Jun 20 '14

What if you were happily developing something in Java or C#, and then another programmer started trying to persuade you to use node.js, and then eventually convinced your management to switch the entire project to node.js?

That's what you're doing when you make people switch to Git.

0

u/[deleted] Jun 20 '14

That's a bit different since you're talking about re-writing significant portions of work. In our case we had to "port over" our packaging scripts but since they're all modular it literally was "replace a cvs packaging script with a git packaging script."

This would be closer to saying we moved from using vim to emacs or something like that.

The point of my post though was that git isn't that hard to learn. It's not 100% consistent sure, and could be improved but it's hardly mind boggling hard to use as some people in this thread make it out to be. Any competent developer who often has to work with way more confusing and incomplete specs/rfcs/etc should be able to figure this out.

1

u/immibis Jun 20 '14

It's also not as great as some people in this thread make it out to be, including you.

0

u/[deleted] Jun 20 '14

Compared to cvs/svn it's miles better. Compared to Hg it's mildly more useful for me (private branching) but I could live with hg if I had to. Compared to private tools like CC and what not it's miles better too. It's simpler (you want complicated try installing CC), smaller, open source, and free.

Realistically if git weren't around I would have pushed our team to move from CVS to Hg because CVS is simply not web-scale (hehehe) but really, it's just not suitable for ad-hoc distributed development.

→ More replies (0)