I guess I'm alone in finding git not that hard to use.
Actually, that's not the point of the article. The point is, git is harder than it should be.
Any halfway competent developer should be able to master git in a couple of weeks
And that is much too much time. I bet you could explain to a fellow developer the foundations of git (commits, DAG, merge…) in a few minutes, maybe an hour. This hours represents essential complexity.
On the other hand, by your own estimation, it would take weeks, to master the current interface. Let's be lenient, an make it days. Those days represent total complexity.
The conclusion is obvious: git's interface has much accidental complexity.
The point of the article is simple: in its current form, git is more complex and harder to learn than it could (and should) be. And that's by a wide margin. This article has convinced me that git can be made very easy to use. So easy that after a day of using a good interface, it would feel easier than subversion, even for hardcore Tortoise users.
Just apply Brett Victor's lessons to this revamped interface, and all will be well.
Realistically by "master" I mean feel comfortable with unconventional merges, cherry picks, patches, rebasing, etc. Day-to-day commits/push/pulls is something you can teach someone in an hour (I do this regularly as I handle the Git training at my office).
It's an argument for ROI though. I've saved quite a bit of time by being able to rapidly branch [or move from branch to branch] as I often handle more than one customer at once. For instance, I'm currently prime on 5 different customer releases most of which are on the master branch (just different tags) but a couple on their own branches. I can easily switch from supporting one customer to another in a heart beat.
That's not something you could do with CVS. Branching in CVS is a huge pain in the ass and merging branches in even more so. In fact we never merged branches in CVS. We only used branches as LTS forks (e.g. version x.foo of something).
Realistically by "master" I mean feel comfortable with unconventional merges, cherry picks, patches, rebasing, etc.
From the look of the mockup shown in the article, it looks like many of "advanced" operations can easily be done after a few minutes worth of learning. I mean, safe rebase and cherry pick with a simple drag and drop, that's even simpler than git add . && git commit! My point stands: with a good interface, you could teach most of the advanced stuff in the time it currently takes you to teach the basics.
For instance, I'm currently prime on 5 different customer releases most of which are on the master branch (just different tags) but a couple on their own branches. I can easily switch from supporting one customer to another in a heart beat.
That's not something you could do with CVS. Branching in CVS is a huge pain in the ass and merging branches in even more so.
That's because under the hood Git is beautiful. Powerful, simple, easy to understand… The only problem is the user interface: complex, inconsistent, perhaps even bloated. It hides the underlying beauty to any novice.
I think this idea of a beautiful model and a crappy interface is supported by the many testimonies that talk about initial difficulties with Git, which suddenly went away the second they heard about the underlying commit DAG.
You know what, I used to think Darcs should have won the DCVS war, not Git. Darcs user interface is simpler, there is less fuss about weird things such as an index, a staging area… To branch, you simply clone (hard links makes cloning fast). A repository is just a set of patches, implicitly ordered by their dependencies. The only thing Git had going for it was history. Commits are explicitly ordered, which can be of great help with things such as bisect.
But with this article, I am beginning to think Git made the better choice. A commit DAG is less flexible than an implicitly ordered set of patches, but it's also more dependable, easier to visualize, and with a good interface, probably easier to manipulate.
3
u/loup-vaillant Jun 20 '14
Actually, that's not the point of the article. The point is, git is harder than it should be.
And that is much too much time. I bet you could explain to a fellow developer the foundations of git (commits, DAG, merge…) in a few minutes, maybe an hour. This hours represents essential complexity.
On the other hand, by your own estimation, it would take weeks, to master the current interface. Let's be lenient, an make it days. Those days represent total complexity.
The conclusion is obvious: git's interface has much accidental complexity.
The point of the article is simple: in its current form, git is more complex and harder to learn than it could (and should) be. And that's by a wide margin. This article has convinced me that git can be made very easy to use. So easy that after a day of using a good interface, it would feel easier than subversion, even for hardcore Tortoise users.
Just apply Brett Victor's lessons to this revamped interface, and all will be well.