Hacker News Reader

Comment by whywhywhywhy | Hacker News Reader

Consider rebranding to a 4 letter name or even better a 3 letter one.

I know it sounds dumb but uv was smart to go shorter than pip and sapphire feels heavier than brew no matter what it does after typing that.

View on HN

The name of the project doesn't need to be the same as the CLI, e.g. Homebrew -> brew.

This could be Sapphire -> sap

I know, probably will, also feel typing out sapphire for the command all the time is annoying + sapp would be weird. For me technical implementation comes first though. I'll do that when something comes to mind

'sph' doesn't seem too bad though.

This reminds me of the PIK image format (a precursor to JPEG XL) whose name happens to be a word for penis in some languages[0]. In the present case "SPH" is a kink/fetish term meaning "Small Penis Humiliation"[1]. I don't know how many people would think of that, though.

I am not sure if the lesson is to try harder to avoid offence, or live with the fact that words can have multiple meanings and we can be "professional" enough to ignore some of those meanings in some contexts.

[0]: https://github.com/google/pik/issues/6

[1]: https://www.urbandictionary.com/define.php?term=sph

Yeah i vote it should be rebranded “why”

command: why install htop, -> install start: because you wan' it -> done: you got it

Something like that you mean?

I would love if the way to respond "yes" to the CLI is "why not"

Why not.

Obvious joke is obvious... but it seems the "motivation" is to write a project in rust.

Perhaps _why?

Maybe `grog` (or `grug` from https://grugbrain.dev)? :)

Reply on news.ycombinator.com