Purity becomes a hard goal when ever you hit the real world at build or runtime. By definition, you have to bridge 2 domains. Imagine constant time compute and

Purity becomes a hard goal when ever you hit the real world at build or runtime. By definition, you have to bridge 2 domains. Imagine constant time compute and constant memory constrains, required in cryptography, being applied to the nix ecosystem. Yes, this is an artifical example but it shows that purity is harder to define and come by, then some people think. Maybe someday these constraints actually do apply to nix goal of reproducibility. With ever changing hardware that purity is a moving target so nix imo will always be an approach to purity and bundling so much tooling is to be expected. Still, you can legitimately call it a hack :)