3 ms·

Ok, but I'm not really looking to my package manager for entertainment. To me this jargon is just needlessly obtuse.

• gmassman 4y ago
  I 100% agree. Cutesy names should end once the package name has been chosen. Package authors and contributors that overdo the thematic names should stick to writing fiction, not code.
  • naikrovek 4y ago
    "keg" and "bottle" are cutesy? well, to see the exact opposite of "cutesy", please fork homebrew and give all of those things GUIDs for names, including all the packages a user could install; you'll soon see why the names chosen are quite acceptable, indeed.
    • deleted 4y ago
      [deleted]
    • bmn__ 4y ago
      This is the worst straw-man I've seen this year. Realistically, non-cute homebrew names would look like bin, libexec, repo, that is to say descriptive names that are already in common use, not GUIDs.
      • naikrovek 4y ago
  • deleted 4y ago
    [deleted]
• tails4e 4y ago
  Yep, I found homebrew confusing exactly because of this 'bespoke' terminology.
  • phantomathkg 4y ago
    I think homebrew is OK. It should be originated from the idea where the install script is user created instead of maintained by the original package author?
• hackernewds 4y ago
  hm quite a sour take. I find that the names actually are reflective of an actual storage process so they fulfill both the playfulness and the natural naming.
  • 1shooner 4y ago
    It's skeuomorphism for the cli.
• geodel 4y ago
  I mean in a way its right. One then need to go for professional companies, sign profession contracts, pay professional service fee and real professional sounding software