Some of the commenters here get hung up on whether git needs undo when nearly all git operations are undo-able. That's just one aspect of the problem: - It is

Some of the commenters here get hung up on whether git needs undo when nearly all git operations are undo-able. That's just one aspect of the problem: - It is evidently difficult for git GUI front ends to implement truly general purpose undo/redo the way any users expect any other GUI to have. This makes discoverability hard, maybe impossible, with a GUI front end to git. - Not all git operations map to the "generic operations on a selection" model most GUI software implements. There is no general "do this to that." - You can create a visualization of a git repo, but that visualization doesn't do a lot for a GUI, because of the lack of a selection or focus. It all still has to be coordinated in the user's brain, which is why most people end up just having to develop a deep understanding of the git command line. GUIs do not take away much, if any, cognitive load. Imagine having to know how a text editor manipulates the structures representing a document. It's hard to think of another design domain that is so intractable for GUI interfaces.