[viraptor]

I think that's the point of the project - to hide the details. I'm a developer of project X, but a user of git. I don't care about it - I want to see it as little as possible, because it's just another tool. Whether it's beautiful or not, I've got a work to do.

It's a bit like with the compiler: it can be pretty and all, but ultimately I just want to write `make` and get my binary. When I need the details, I know where to find them.

[schacon]

I would argue that your SCM tool should be less like a compiler that just needs to get out of your way and just do it's job how you expect it and more like a text editor. Do you use emacs or vim, which have learning curves but are powerful and help you ultimately do your job much better and more efficiently? Or do you use Notepad, which just edits text and who cares? I think most developers prefer Emacs or Vim or even an IDE. You invest time in a more complex tool so that you can be a better developer.

That being said, I think this will be useful for a lot of less-techy designers or copy-editors or QA people, etc. People who can just open stuff in Notepad because they don't need to craft code.

[sh1mmer]

I think the argument here is that

a) basic Git isn't that complex b) Learning a dumbed down subset of Git won't help you long term

I would say that giving people a gentle introduction to stuff is great, but it's important to make sure that it is a launch-pad for really learning the tool properly in the future.