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.
Re:Homebrew 1.2.0
by bobwaycott on Monday May 01, 2017 @05:04PM
(#14241564)
May I consider using the names tableturd and puddlecuddle for future ideas? :)
Re:Homebrew 1.2.0
by lalaithion on Monday May 01, 2017 @08:09PM
(#14242934)
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?
Re:Homebrew 1.2.0
by PascLeRasc on Tuesday May 02, 2017 @07:30AM
(#14245503)
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?
Re:Homebrew 1.2.0
by joshmanders on Monday May 01, 2017 @05:17PM
(#14241723)
It's free and you are allowed to criticize it.
But we're also allowed to criticize your criticism too.
Re:Homebrew 1.2.0
by thatswrong0 on Monday May 01, 2017 @06:18PM
(#14242239)
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".
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. -.-