Screaming in the Cloud How Homebrew Became Mac's Package Manager with Mike McQuaid
11 snips
Jan 27, 2026 Mike McQuaid, project leader of Homebrew and steward of the macOS/Linux package manager. He recounts Homebrew’s pub-born origin, the rise of Brew Bundle for one-command Mac setups, casks for GUI apps, auto-update tradeoffs that support millions of users, maintainer stipends and review-based security, and why Homebrew enforces strict open source rules.
AI Snips
Chapters
Transcript
Episode notes
Homebrew As A Cross-Platform Tool
- Homebrew supports Linux because users needed a non-root, cross-platform package manager for development and CI.
- Some Linux distros now use Homebrew alongside immutable roots and Flatpak for userland packages.
Born In A London Pub
- Homebrew was conceived by Max after a pub conversation about package management, inspiring the beer-themed names.
- Casks began as a separate project to manage macOS apps like Chrome and were later merged into Homebrew.
Rebuild A Mac With One Command
- Use Brew Bundle with Brewfiles to export and install your exact set of packages for a new machine.
- Run brew bundle dump, review the diff in git, then brew bundle cleanup to remove unneeded cruft.