Hacker News Reader

Comment by xz0r | Hacker News Reader

Its explained at the very beginning of README :) https://github.com/Homebrew/brew/blob/master/docs/Formula-Co...

Yay more words and concepts to add to my cognitive load. We already have established terms for these things but why use package and repository when you can invent tableturd and puddlecuddle?

When it comes to UI it sometimes feels like programmers go out of their way, to make software get in mine.

I'll take it, but I'll keep rolling my eyes and sighing. -.-

May I consider using the names tableturd and puddlecuddle for future ideas? :)

>Yay more words and concepts to add to my cognitive load. We already have established terms for these things but why use package and repository when you can invent tableturd and puddlecuddle?

Why volunteerily start, develop, and maintain a package manager and its repository, if random people are gonna try to dictate even how you name your packages?

Here we go again with another variation of "it's free so you are not allowed to criticize it".

Can we move on as a community and drop this?

It's free and you are allowed to criticize it.

But we're also allowed to criticize your criticism too.

One is legitimate criticism: "It would be easier to use this software if it used more conventional naming."

The other isn't even close: "Instead of criticizing this free software, write your own".

Disagree and commit - Bezos

Yea, I agree, I thought it was cool/clever to start out with but I have to reference the jargon when I revisit modifying formula or making bottles, usually there is a long enough hiatus from messing around with homebrew that I forget.

Some terms are useful if they're unique. Which is easier to remember: a uniquely named directory called `Cellar/`? or another `bin/` somewhere in the filesystem?

One of the best parts of open source software is that you can fork it and change whatever you want.

Indeed, but when I read that a Keg is an "installation prefix" and a Bottle is a "Pre-built Keg" I give up.

A "keg" refers to the whole directory structure associated with an installation. A "bottle" is just a tarball containing that structure from a build on the CI, rather than a from-source installation.

Still doesn't make any sense whatsoever.

You had me at directory structure. Then you lost me at "bottle", had me at tarball again, but by then I was exhausted and don't care any more.

Terminology is important because it has application for the end user. I don't get any use out of tap/keg/cask.

It makes sense but, like you said, you're exhausted and don't care.

Bottles (binary installations) are an addition to Homebrew; it was originally a source-only "package" (really just Ruby scripts that downloaded tarballs and ran `make`) manager.

Terminology is important. However, the standard terminology of package management does not always map cleanly to Homebrew's behavior. If the options are inventing our own terms or using preexisting ones unlike everybody else, I'll always go with the former.

Edit: I'm mostly thinking of things like "keg" and "bottle"; "tap" could indeed be replaced with "third party/external repository", and a "formula" could be called a "package description" or something equally generic.

Reply on news.ycombinator.com