HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Homebrew
brew
Ruby2016–2026
Homebrew / brew

brew

đŸș The Package Manager for Everywhere

158Distinct people
201Mentions
0Explicit recommenders
50.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

đŸș The Package Manager for Everywhere

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 12:01:57 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year201 dated mentions

Observed mentions: 2016-04-04 18:36:42 UTC to 2026-09-13 13:02:51 UTC.

010203040502016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 47 mentions; 7 submissions, 40 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 16 mentions; 0 submissions, 16 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 13 mentions; 0 submissions, 13 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 29 mentions; 6 submissions, 23 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 36 mentions; 3 submissions, 33 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 9 mentions; 1 submissions, 8 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 15 mentions; 3 submissions, 12 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 9 mentions; 1 submissions, 8 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 9 mentions; 0 submissions, 9 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC47740
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC16016
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC808
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC13013
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC29623
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC36333
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC918
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC15312
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC918
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC1019
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC909

What Hacker News says

9 sources
I'm a Linuxbrew user, too, even on top of normal Ubuntu distros because (a) the rapid release cycle you mentioned (b) because so much of my workflow is built on top of Homebrew it was natural for me to just continue using it when I used Ubuntu at work I will also confess(?) that I run it in "unsupported mode"[1] because (a) I often need to fix bugs in the software and tweaking ${whatever}.rb and $(brew reinstall -s -v $whatever) makes that painless (b) I keep my actual $(brew repo) pretty dirty, too, to cure a lot of stupidity introduced by running it in unsupported mode :-D I actually would guess some of the patches would be valuable to the wider community but I lump Homebrew and Elastic into the "I don't have enough emotional energy to survive their PR process" camps 1: I don't have the finger-wagging link handy, but McQuaid used to rea
Read the rest
lly get bent out of shape about people running --build-from-source; it seems they've changed their mind https://github.com/Homebrew/brew/blob/4.4.6/docs/FAQ.md#can-...
In Homebrew Is Great on Linux
Seems like it could live among these: > We currently demand that users internalize several metaphors when interacting with Homebrew. These include: > Formula (how to build a bit of software) > Bottle (pre-built software) > Cask (pre-built software on macOS) > Tap (a collection of software) > Keg (where software installs itself) > Cellar (where all my software install themselves) > As well as an additional number of less-common metaphors that contributors and maintainers need to know, like Rack, Tab, and Formulary. https://github.com/Homebrew/brew/issues/10798
In Toasts are bad UX
I don’t really understand what the problem you’re referring to is: /usr/local is explicitly the non-OS software hierarchy, which is why Homebrew used it. When Apple Silicon came out, the prefix was changed as part of allowing native and Rosetta-driven Homebrew installations to co-exist. There’s no nefarious reasoning behind it. Edit: a thread with a bit of the history can be found here[1]. [1]: https://github.com/Homebrew/brew/issues/9177
In Our audit of Homebrew
I’m a bit puzzled by the wording of this blog post, because it says you’ve worked with Homebrew to do this audit, but your name sounds familiar to me, and indeed if we check Homebrew’s README [1]: > Homebrew's maintainers are [
long list of names
] William Woodruff [
] [1]: https://github.com/Homebrew/brew Is there any reason this is not mentioned in the blog post? I don’t think it would make a difference, but just to clarify things.
In Our audit of Homebrew
itbroke·Jan 12, 2024Submission

Tell HN: GitHub broke feeds for individual commits

We can append .atom to certain GitHub URLs to get a feed for that page. For example, this is the releases page for Homebrew: https://github.com/Homebrew/brew/releases If we append .atom: https://github.com/Homebrew/brew/releases.atom We can now subscribe to be notified of releases in an RSS reader. This used to work for the commit history of individual files. Let’s say we wanted to be notified for changes to Homebrew’s python alias. First we’d open the commit history page: https://github.com/Homebrew/homebrew-core/commits/master/Aliases/python Then append .atom: https://github.com/Homebrew/homebrew-core/commits/master/Aliases/python.atom Except now it returns JSON output. Not only does this prevent checking for changes to individual files in an RSS reader, the extension is misleading. If you have any scripts that parse
Read the rest
the feed or are tracking changes to any file in an RSS reader, those are now broken.
5 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.