About using Nix in my development workflow

Re:About using Nix in my development workflow by Cedricgc on Wednesday July 20, 2022 @09:50PM (#32174841)

Yes, derivations are the main primitive to target in an agnostic way

Main challenge is the value of the nixpkgs repo is enormous, and that looks tightly tied to Nix the language and its implicit constructs. I think instead of an FDI one would have to provide a true competitor that is more attractive on multiple dimensions like:

- reworking Nix as more a modular architecture (see Tvix: https://tvl.fyi/blog/rewriting-nix)

- Tackling a package repo and Nixos equivalent with day 1 reproducibility (not just repeatability) like https://reproducible-builds.org/

- Better UX experience on the "entrypoints" of Nix like home-manager and dev-shell flakes - I think CUE has some nicer language features for this and does not require figuring out derivation generation, just referencing the existing nixpkgs set

[ Parent | on HN ]

Re:About using Nix in my development workflow by mschwaig on Thursday July 21, 2022 @07:31AM (#32178109)

Thanks, I had not heard of Tvix yet.

What do you mean by day 1 reproducibility instead of repeatability? Isn't tracking and eliminating nondeterminism a gradual process anyways?

I don't see how nixpkgs or NixOS is a faulty basis for that kind of work, since I have not run into any flaws with regards to reproducibility that I thought would be easier to address on a clean slate basis.

[ Parent | on HN ]