Curious bout your use case for building all software from source, is it because you're worried about the supply chain since nixpkgs builds don't have reproducibility guarantee?
> With a sufficient number of users of an API,
it does not matter what you promise in the contract:
all observable behaviors of your system
will be depended on by somebody.
But we didn't have pressure to switch from C to Python & solved it down our throats by management, or social media telling us if you don't use Python you're getting left behind, did we?
In C vs. Python case, we know about technical trade-offs and when to use what, but in AI productivity neratives, we keep pretending that technical or cognitive debt created by AI doesn't exist.
Sure, person A can be 20% "faster" and suggest that this tool increases productivity by a magnitude, but if it costs person B 50% more time to review A's slop or clean up A's mess, the team's productivity doesn't really increase.
Git itself is decentralized, and we can use email to send patches, but GitHub's role is more like a social network to discover and "star" projects.
I really hope Forgejo/Gitea can get federation to work to the point where we can ditch GitHub, they already have the federated star feature [1] - I'm doing my part by hosting my own Forgejo instances and using Woodpecker CI + my own CI/CD system, and it's faster than GitHub Actions.