4 ms·
Git has a reputation for having one of the most confusing CLIs ever. However, it's probably better to decide what operations you want to do and work from there
by goku12 3y ago
Git has a reputation for having one of the most confusing CLIs ever. However, it's probably better to decide what operations you want to do and work from there to find out the commands needed. That obviates the need to learn so many commands and switches - for me, at least. My training material was also designed like that. My students use them like cheat-sheets until they get familiar enough.
- magicalhippo 3y agoThe thing is, I want to design and write code. I don't want to remember a bunch of command line parameters for other stuff. With Mercurial I didn't have to, it just flowed.
- Espressosaurus 3y agoI know the operation I want to perform. I even know approximately what it's called. I can't be bothered to remember what obtuse syntax is required to invoke it. Rebasing isn't difficult, merging isn't difficult. Staging is stupid so I ignore it. The stash is stupid, so I ignore it (why not just make a new branch and commit?). Bisecting isn't difficult. Seriously, the concepts are not rocket science. Git just makes it hard to remember how to correctly invoke the thing you want to do for no good reason other than that it was hacked together in a fit of pique and those decisions have stayed with us ever since. And a lot of the functionality is centered around an email-based workflow, which makes sense for the Linux kernel, and doesn't make sense for anybody else.