You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 🤔
The text was updated successfully, but these errors were encountered:
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 🤔The text was updated successfully, but these errors were encountered: