He is the author of one of the popular Erlang books and here talks about using Nix in production instead of just pure langauge specific package managers (or OS package managers).
Some really good insights on immutability, reproduceability, and of course real production use examples.
Yes Nix, but Nix that uses IPFS (https://ipfs.io) as a distribution medium for packages. This was a package will stay published as long as someone is using it.
Yeah, they're getting there. The binary package cache is a start. If it cached upstream tarballs and git revs as well as builds, it would mitigate the sort of thing the OP talks about.
Nix still needs some sort of distributed trust model, though. Without that, nixos.org is a single point of failure.
https://www.youtube.com/watch?v=xRSFJH3Lw6I
He is the author of one of the popular Erlang books and here talks about using Nix in production instead of just pure langauge specific package managers (or OS package managers).
Some really good insights on immutability, reproduceability, and of course real production use examples.