3 ms·
I think these a a good set of medium/long term goals. "flake.nix in every repo" seems a bit of a chicken & egg thing relating to "nix should work reliably ever
by rgoulter 4y ago
I think these a a good set of medium/long term goals.
"flake.nix in every repo" seems a bit of a chicken & egg thing relating to "nix should work reliably everywhere". If nix runs into problems with common situations, it's less likely there'll be a flake.nix. But, if it's rare to spot a flake.nix file, it's harder to be interested in nix.
Rather, I think most of the comments I see from people who are less than happy about nix as-is relates to friction from trying to use nix, but things go wrong.
- baby 4y agoIMO nix should not get in places where package management is done correctly (rustup/cargo), but definitely should when it's not done correctly (OCaml, C, python, etc.)
- mplanchard 4y agoWe use nix for our rust projects, for the following: - consistent dev environment with all local dependencies (postgres, rustc, awk, etc.) - building rust packages themselves - building tiny docker images that run rust binaries The official Rust tooling for nix still uses Cargo under the hood, and this makes it way easier to use and more consistently functional than the equivalent tooling for Python, JS, and similar, at least in my experience