▲ | trod1234 7 days ago | |||||||
The problem with Nix is that its often claimed to be reproducible, but the proof isn't really there because of the existence of collisions. The definition of reproducible is taken in such an isolated context as to be almost absurd. While a collision hasn't yet been found for a SHA256 package on Nix, by the pigeonhole principle they exist, and the computer will not be able to decide between the two packages in such a collision leading to system level failure, with errors that have no link to cause (due to the properties involved, and longstanding CS problems in computation). These things generally speaking contain properties of mathematical chaos which is a state that is inherently unknowable/unpredictable that no admin would ever approach or touch because its unmaintainable. The normally tightly coupled error handling code is no longer tightly coupled because it requires matching a determinable state (CS computation problems, halting/decidability). Non-deterministic failure domains are the most costly problems to solve because troubleshooting which leverages properties of determinism, won't work. This leaves you only a strategy of guess and check; which requires intimate knowledge of the entire system stack without abstractions present. | ||||||||
▲ | anotherhue 7 days ago | parent [-] | |||||||
Respectfully, you sound like AI. I expect you don't trust git either, especially as its hash is weaker. A cursory look at a nix system would also show you that the package name, version and derivation sha are all concatenated together. | ||||||||
|