There's a selection of ways that may or may not work for you:

- `formula@version` packages

- `brew version-install` (which uses `brew extract` and `brew tap-new` under the hood)

- `version_file:` support in `brew bundle

- `brew pyenv-sync`

Have a look at https://mise.jdx.dev/, it's exactly what you're looking for!

Yes, exactly. The goal is you can install all official packages without needing custom postinstall/preflight/postflight blocks.

You can have multiple versions of tools installed. But overall, homebrew plays well with atomic distros. They are thing in itself, yet getting more popular lately. Im using them at home and on the server, and it feels calmer, because I can't fuck up whole system easily. Considering I'm using llms without sandbox often, this is pure gold.

Homebrew provides access to a massive catalog of software, including many tools that are not packaged for Fedora, Debian, or Ubuntu. Homebrew relies on a high level of automation in GitHub actions, which ensures users get the latest versions of tools quickly, rather than waiting for distribution-specific repositories. The Homebrew approach also decouples the underlying system from what you choose to install in user-space.

You can run Homebrew on Linux without admin privileges. Useful e.g. for shared hosting.

macOS Permission Management regarding shell scripts is so bad. For example they show you a list of software thats allowed to access the full disk - but I have like 8 "sh" or "bash" in there and some random scripts with no way to open the enclosing directory in Finder making it basically impossible to see what it is and if its legit…

We should all be ashamed of the interview culture we have created in this industry.