3 ms·
The CLI is indeed hard to learn. But the simplicity of git is not using it, it's its internal structures: http://eagain.net/articles/git-for-computer-scientist
by jstimpfle 10y ago
The CLI is indeed hard to learn. But the simplicity of git is not using it, it's its internal structures:
http://eagain.net/articles/git-for-computer-scientists/ http://eagain.net/articles/git-for-computer-scientists/
If you understand these, then three stages to "commit to server" won't seem too many to you. (Often you don't need the index-building stage ("add"), and then you can say "git commit -a").
What people complain about is often the CLI's inconsistency. For example "git branch -d" vs "git remote rm" to delete things. Then some things you want to do can be achieved with more than one sub-command in totally non-obvious ways. And some sub-commands do more than "one thing", like "checkout".
- masklinn 10y ago> But the simplicity of git is not using it, it's its internal structures: It's great that you can masturbate over it but I don't give a rat's ass, I just want to safely store and share my code with a VCS. I'd rather mercurial or darcs had won as they have sane (or even delightful) CLI, sadly the world disagreed. That git's porcelain is a giant abstraction leak of the internal structures and plumbing is not a feature.
- philjohn 10y agoYou shouldn't have to learn how the data structures of the tool work beneath the surface to successfully know how to use a tool.
- zajd 10y agoYou don't have to. The difference with git is that it's even possible.
- cies 10y agoWhy wouldn't it be possible with Gitless to learn the data structure?
- jstimpfle 10y agoI think you should learn them, but ideally it should be obvious from using a tool what its internal data structures are. For persistent data structures simplicity, transparency and stability are very important.