3 ms·
Several of the authors complaints stem from him not using temporary branches liberally. I think he’s suffering from the common beginners’ problem of thinking th
by Myrmornis 9y ago
Several of the authors complaints stem from him not using temporary branches liberally. I think he’s suffering from the common beginners’ problem of thinking that committing has to be final. The word “commit” doesn’t help; “snapshot” might be a better metaphor. But even if you understand that a commit is cheap, and disposable, it takes quite a bit of experience to get comfortable using the graph comprising different branches, and to be confident with remote and local branches. This learning curve could be said to be a problem, but personally I don’t really want software engineers as colleagues if they can’t learn git.
- kartickv 9y agoAuthor here. You're right -- I haven't created even one branch so far, let alone liberally. But snapshotting should be automatic, like in Google Docs. It's not that someone "can't learn git". Learning is a process, and takes time. But I have no sympathy for tools with an unnecessarily steep learning curve and poor UX like Git. I should have to pay that price only when I want to do something very sophisticated that only Git can do. Not for basic tasks. Simple things should be simple and hard things possible. Snapshotting should be automatic.
- Myrmornis 9y agoOK, I hope the tone of my original post wasn't unpleasant (on re-reading, not sure I'm a huge fan of it). It might be interesting to have a version control system which does continuous recording. If git is the last word in VCS then I guess humans didn't live for much longer! But personally I am completely happy with the current style in which the user explicitly creates snapshots and these form a distributed graph, and the user is given tools to work with the graph.
- kartickv 9y agoThanks for clarifying tone.