4 ms·
> as if Git’s command-line interface were already the pinnacle of usability. It is, for me. I love git and checking in my progress in small chunks that make se
by fxtentacle 4y ago
> as if Git’s command-line interface were already the pinnacle of usability.
It is, for me. I love git and checking in my progress in small chunks that make sense to me is very easy with the command line tools. They're also easy to integrate and automated. Maybe they truly are the pinnacle of usability?
As another example, compare cashiers using one of those DOS GUIs with modern ones using touch screens. The simpler GUI works much faster, once mastered.
- stephen_g 4y agoYeah, I’ve never had a problem with it. I mean, sure it’s not perfect but I really don’t get all the hate.
- CivBase 4y agoI think the hate comes from it not being very "noob friendly". It's designed for power users who are familiar with how git works. In my experience, most git users don't really know how git works fundamentally. They just learn the commands for a particular workflow and stick to that. That's how I started. I've seen this to be especially true for developers coming from SVN or another centralized versioning system.
- howinteresting 4y agoA very basic issue with git is that if you're editing a stack of commits, you can't go back to an earlier commit without completing the rebase -i and restarting it.
- cryptonector 4y agoNot quite true. You can add `exec git branch progressN HEAD` every so often in the `git rebase -i` script, or you can `edit` commits and before `git rebase --continue` do `git branch progressN HEAD`, then later if you need to abort and restart your rebase you can rebase --onto one of those saved HEADs.