-
-
Notifications
You must be signed in to change notification settings - Fork 13.5k
hf: renamed from huggingface-cli #231234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
hf: renamed from huggingface-cli #231234
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hfas a formula name seems terribly non-descriptive. The formula name doesn't always have to match the name of the program it installs. Maybe we should just add anhfalias instead?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have a super strong opinion here, but I think we need to come up with a standard convention to handle tools like this.
gh, which is the binary name.awscliand the binary isaws.There are a few other options that we have as
foo-cliwhere the binaries are justfoo. We should try to standardize one way or another.cc @Homebrew/core for thoughts.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ghseems more likely to be more widely recognised, but I'm not opposed to having it be namedgithub-cliinstead.awscliseems sufficiently understandable enough on its own to not require expansion.But standardising this would be good; I agree.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
HuggingFace CLI is not as popular as
ghorrg, but it is still quite popular.Having a short name has more benefits than hunting for a long name. If you don't know what a tool does, the long name won't be descriptive anyways in majority of cases.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changing the binary name seems fine, but I am not sure about the formula. Others have already mentioned the same thing, but when I see the name
hf, nothing comes to my mind.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am sure it make sense to suffix all commands with
-cli, because the majority ofbrewpackaged software is CLI.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
jjis another pretty terrible name. That one should be namedjujutsu(and need not be suffixed with-cli)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For automation and simplicity it is more beneficial to have packages named after binaries. Otherwise scripts need to maintain additional mapping. For example you need to know that to get
fdon Ubuntu, you need to installfd-findpackage. Digging for a "proper" package name is a waste of time when you know exactly what you need. Also, people will have to spend time to maintain mapping for missing commands suggestion scripts.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure I follow. I'm not proposing that
brew install jjnot installjujutsu, or thatbrew install hfnot installhuggingface-cli, so I don't see why scripts needs to maintain additional mappings.I just want formulae to have names that are easier to understand and easier to look up. For example, Googling
jjdoes not return any useful results for me. The first result is the Wikipedia page of a singer named JJ, and the second result is that same singer's Instagram account. Googlingjujutsu, on the other hand, at least returns the CLI tool's repo as the third result.This is part of why I disagree with:
There is certainly a set of users who won't recognise a package with both its short name (e.g.
jj) or long name (e.g.jujutsu). But it does seem likely to me that there are users who would've recognised the long name but not the short one, and anyone who recognises the short one would probably recognise the long one too.That is to say: the longer name is, almost by definition, more descriptive than the short name, and therefore almost always more useful.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we shouldn't have a standard convention or at least the standard convention should not be one that results in consistency between tools.
Our convention should be "what do the upstream authors refer to the tool as" and/or "what do the users refer to the tool as".
Having a look at the website here, I don't think there's a good argument for renaming.
We literally have aliases for reasons like this. Perfectly happy to have a
hfalias added in this case.Furthermore, given renames/migrations are not transparent and 100% without cost to the user (even just time/output): we should avoid renames unless pressing. Mass renames for "consistency" are just annoying and messy.
Good case study: go visit https://github.com/jj-vcs/jj and that's what it's referred to as.
Then again, in this case at least the actual GitHub repository is called
jjwhich is an argument for the naming.This is good reasoning.
This is very bad reasoning.
I agree. This also goes for variables, for what it's worth.
Passing on this PR.