Walk in any Rails developer office and look at the words written on the whiteboard - you never know if it's a list of gems or a they're having a schizophrenic episode

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. -.-

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.

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

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.

>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

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.

I still use MacPorts, because I find cutesy metaphors offputting.

I've never worried about it. I just

brew install thing-i-want

Sure, but the moment you have to do anything slightly non-standard you get stuck in jargon land

For like 2 minutes... And then you don't have to think about it for the rest of your life...

Until the next time, when you need to either remember what you did once a couple months back or relearn it again.

The metaphors could be a little bit clearer.

If only there were a site on the internet where you could search for these things....

There is, but that's a waste of my time, when we could all just use normal words.

Yea, like grep and awk!

Naming things has always been hard.

Grep and awk were a new thing decades ago. I expected we knew better now, but, it seems, we are doomed to ignore the past and go reinventing (and then having to fix) our own square wheels.

Yeah...if only I didn't have to press one for "English"

That kind of defeats the purpose of a software manager, doesn't it?

Like what?

I still use MacPorts, so I don't worry about it either.

As do I. MacPorts has fit my mental model in a way that Homebrew never did.

I've always used Macports, quite solid. Also, the whole "screw Google because they wanted me to know a basic algorithm" drama was off-putting for various reasons.

It'

It isn't particularly friendly to non-native English speakers... stick with the standard jargon please!

This seems to be a common problem with Ruby projects. fastlane.tools is incredibly popular for automating iOS development. "gym" is the subcommand to build an app, "scan" runs tests, "sigh" fixes code-signing etc.

There seems to be sizable chunk of people who agree (myself included).

At this juncture (1.2 and rather successful) is there any feasible way for the maintainers to switch the nomenclature to something a tad more literal/expressive?

I agree that the jargon needs improved. The hard balance is figuring out natural names for things that don't make things harder for existing users to understand.