6 ms·

I wish they made a breaking change in the next version and make the CLI actually usable. Before you downvote, ask yourself how do you list tags, branches and r

I wish they made a breaking change in the next version and make the CLI actually usable. Before you downvote, ask yourself how do you list tags, branches and remote

School-Cotton 4y ago
They shouldn't break the existing `git` command as it is widely used in scripts. But there are projects that try to build better UIs on top of git; the most serious such attempt that I know of is magit.
ajross 4y ago
"git tag", "git branch -a", "git remote -v" You point is what, that these are needlessly asymmetric? It's true. But they're in my head because I do them every day, and it's not like I'm suffering under the burden of remembering a handful of flags. That's a pretty far cry from "not actually usable", so maybe your hyperbole is a little misplaced?
- ArrayBoundCheck 4y ago
  Correct. That was a simple example that's easy to understand Anyone with half a brain can understand that if they can't keep something as simple as printing a list consistent you better believe nothing else will be straightforward. Which is my point. NOTHING is straightforward and I haven't met a single person who likes the CLI if they do anything more complex than a commit, push and pull. I know people who still refuse to use rebase and don't understand bisect or blame. They use a GUI to restore files
PeterWhittaker 4y ago
Branches are easy, what with them being only labels: > git branch --all Tags are different, since they are actual objects in git, but using ls-remote isn’t tough, and one could create an alias.
mmcclimon 4y ago
While acknowledging that git's CLI is often unintuitive: `git tag` lists tags, `git branch` lists branches, and `git remote` lists remotes, so I don't think I understand this particular objection.
- ArrayBoundCheck 4y ago
  Compare it with `git branch -a` and `git remote -v`. That's my point. Not only are they all different flags but you'll get half the data you could be getting and not know why. It's impossible to google
CRConrad 4y ago
> I wish they made a breaking change in the next version and make the CLI actually usable. As I understand it, they're attempting to make it "actually usable" by adding more consistent (and maybe even "intuitive") options to the syntax. In order to avoid a breaking change, though, they're also leaving the old confusing stuff in. Sure, it's regrettable that it's there in the first place, but understandable that they don't want to break people's scripts from, by now, decades back. Sure, that makes it a little harder to learn, but it can be done, by just making a conscious decision to ignore those crufty old bits.

I wish they made a breaking change in the next version and make the CLI actually usable. Before you downvote, ask yourself how do you list tags, branches and remote

School-Cotton 4y ago

They shouldn't break the existing `git` command as it is widely used in scripts. But there are projects that try to build better UIs on top of git; the most serious such attempt that I know of is magit.

ajross 4y ago

"git tag", "git branch -a", "git remote -v" You point is what, that these are needlessly asymmetric? It's true. But they're in my head because I do them every day, and it's not like I'm suffering under the burden of remembering a handful of flags. That's a pretty far cry from "not actually usable", so maybe your hyperbole is a little misplaced?

ArrayBoundCheck 4y ago
Correct. That was a simple example that's easy to understand Anyone with half a brain can understand that if they can't keep something as simple as printing a list consistent you better believe nothing else will be straightforward. Which is my point. NOTHING is straightforward and I haven't met a single person who likes the CLI if they do anything more complex than a commit, push and pull. I know people who still refuse to use rebase and don't understand bisect or blame. They use a GUI to restore files

PeterWhittaker 4y ago

Branches are easy, what with them being only labels: > git branch --all Tags are different, since they are actual objects in git, but using ls-remote isn’t tough, and one could create an alias.

mmcclimon 4y ago

While acknowledging that git's CLI is often unintuitive: `git tag` lists tags, `git branch` lists branches, and `git remote` lists remotes, so I don't think I understand this particular objection.

ArrayBoundCheck 4y ago
Compare it with `git branch -a` and `git remote -v`. That's my point. Not only are they all different flags but you'll get half the data you could be getting and not know why. It's impossible to google

CRConrad 4y ago

> I wish they made a breaking change in the next version and make the CLI actually usable. As I understand it, they're attempting to make it "actually usable" by adding more consistent (and maybe even "intuitive") options to the syntax. In order to avoid a breaking change, though, they're also leaving the old confusing stuff in. Sure, it's regrettable that it's there in the first place, but understandable that they don't want to break people's scripts from, by now, decades back. Sure, that makes it a little harder to learn, but it can be done, by just making a conscious decision to ignore those crufty old bits.