Post

Remember that experiment of using @flox.dev to replace Homebrew? Now it's official. flox.dev/docs/tutoria...

> You need a broader set of software. Homebrew has a sizeable collection of packages, but the Flox Catalog is based on Nixpkgs, the largest collection of packages in the world. I publish a couple of binaries to homebrew, do I now need to also publish them with nix or to nixpkgs?

to be honest, as a project maintainer, the proliferation of package managers has been annoying. We have actually gone the opposite direction to simplify and have decided to only support binary downloads from github and our homebrew tap.

What ecosystem? I presume something supporting static builds?

Go

I believe the @flox.dev team is working on something like this.

We are! It's not all done yet, but if you're interested and want to try some things out, hit us up in our community slack. (using bitly because the whole URI is super long and ugly) bit.ly/3D8jbDX