Coming from Mac centric ruby teams, we commonly mention installing things with 'brew' as part of how to get a local environment setup. The theory usually being that the linux devs usually will confidently use their own package manager and the well I havent worked with many windows devs.
In theory having brew as a workable options for teams that are on mac and/or linux, provides for a nice cross-platform base for documentation.
Interested in others views around documentation for teams in this area.
evolve2k•3h ago
Homebrew can be useful for installing packages that aren't easily available on your distro. For many software programs, you may need to use Flatpak, Snap, or install from source. Using Homebrew can make it much easier to install and maintain.
For some distros, finding an updated package is difficult. You either have to deal with an outdated package or get the updated one via cumbersome means. If that package is available on Homebrew, you can easily get the updated one using a single command.
In the upcoming days, I can see myself continuing to use Homebrew on Linux for managing Linux packages due to its quality of life features and rich documentation. Especially if you're a developer, you're bound to love it.