3 ms·
I held out for more than a year and then gave in. Having to research, find, and learn a new git GUI was going to cost me more than $70. So I've punted the prob
by atonse 4y ago
I held out for more than a year and then gave in. Having to research, find, and learn a new git GUI was going to cost me more than $70.
So I've punted the problem for another year. But I strongly agree that it's absolutely the wrong fit for this kind of app. They will start adding all kinds of bloat just to justify the monthly fee.
- colinjoy 4y agoNot researching, finding and learning a new git GUI is also going to cost you more than $70. Year, after year, after year ...
- BiteCode_dev 4y agoOne more reason to learn the command line. Once you know how git cli works, any UI is easy to understand. No vendor lock in.
- hombre_fatal 4y agoA gui adds a lot on top of a git cli for me. Scrolling diffs/history and adding/removing staged lines alone is better. Using a gui doesn’t mean you didn’t arrive there deliberately.
- atonse 4y agoI actually do almost everything in the CLI (checkouts, pull/push, branches, most no-conflict merges, most rebases, tags, etc), however when you're rebasing, messing with branches and merges, nothing beats a visual medium to just even look at the graph and make sense of it.