Earlier quoted context omitted.
Cabal has had nix-style local builds since 2016: https://blog.ezyang.com/2016/05/announcing-cabal-new-build-n... https://cabal.readthedocs.io/en/2.0/nix-local-build-overview... Also cabal isn't positioned to be a system level package manager. Haskell programmers are the type to want both their application builds and system dependencies to be reproducible and predictable. > Stop being lazy, go back to engineering firs…
Cabal has had nix-style local builds since 2016: That's a bug not a feature. Every language these days is trying to force you to use its own badly-implemented imitation of Nix. Just look at what cargo does with the target/ directory and wonky "build fingerprints". It's madness.
As it is, the rust-in-Nix and bazel-in-Nix stories are both pretty terrible, while the Python one is actually not too bad: https://github.com/nix-community/poetry2nix (barring these 4000 lines of horrible hacks: https://github.com/nix-community/poetry2nix/blob/master/over... and these 27000 lines of telling Nix which Python buildsystem every package ever happens to use: https://github.com/nix-community/poetry2nix/blob/master/over...)