Skip to content
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

pico-init command is inconsistently named #148

Open
xiorcale opened this issue Aug 27, 2024 · 0 comments
Open

pico-init command is inconsistently named #148

xiorcale opened this issue Aug 27, 2024 · 0 comments

Comments

@xiorcale
Copy link

Not a bug, but I find it strange that the command to initialize the VSO subsystem is called pico-init.

I don't really see what extra information does this bring?
On top of that, if we look at the other commands from cmd/pico.go, none of them are prefixed with pico-.

So, why not just keep it simple and call it vso init, wouldn't this be a more consistend user exprerience?

p.s. I see that it was actually called init in the past: 432f0da, so I'm really curious to understand what motivated this change 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant