4 ms·
You can do all of that with any programming language, that is not a special trait of Nix. Your lack of insight into what people actually want betrays your need
by oneplane 3y ago
You can do all of that with any programming language, that is not a special trait of Nix. Your lack of insight into what people actually want betrays your need to promote nix. You can also use nix to automatically make sure that you install the latest version of something, and that means that if you rebuild at different times you get different results. That is working as intended, but having looked around this is because we use niv everywhere because we really don't want to waste time on manual version management, that's what computers are for.
Edit: come to think of it, this is probably why we stopped using nix for new projects. Having to wrap nix a lot to make it work with reality makes it a bit pointless.
Anyway, Nix isn't the box, and it still will never be the box. It doesn't matter that it could be the box, because the people that want the box are not the people that can utilise nix. This Venn diagram just doesn't intersect.
As for your insistence that it's bit for bit guaranteed: you do really think that anyone in the world who is just looking for a box gives a crap? It doesn't matter how deterministic it is, or how nix does it better than anything else, because the entire factor of determinism doesn't matter in this case.
- kreetx 3y agoI'm sorry to hear that you've had a bad experience with it, it does take a while to get used to. I guess there is still much UX work to be done there.
- oneplane 3y agoI personally still use Nix, but it's not something that has stuck in any work environment so far.
- k8svet 3y agoSorry, but this is just nonsense. You have to intentionally use Nix in a way that no one does, in a way that is highly discouraged in every corner of the community, in order to get unreproducable behavior. Furthermore, that mis-usage does not apply to any way that Nix is actually shared amongst peers (a nix-shell or flake). The only way this is true is if you're sending around a list of pacakges, telling users to install them manually, not pinning nixpkgs, not using a flake. Aka, a situation I've literally never seen or heard of. Ever. Worst case a user comes and asks how to make `nix-env -i` portable and the community collectively gasps and discourages the behavior. I'm not advocating anything. I acknowledged Nix has a learning curve. I have countless issues opened for UX nags. I'm combating outright FUD and ... I don't want to say... at this point. >As for your insistence that it's bit for bit guaranteed: you do really think that anyone in the world who is just looking for a box gives a crap? It doesn't matter how deterministic it is, or how nix does it better than anything else, because the entire factor of determinism doesn't matter in this case. Move those goalposts and ignore the other benefits that spoke to the desire use-case, again, sure! EDIT: Oh brother, a niv user. Never mind, ignore my post, you probably already know it and don't care. Not worth the time for either of us. Implying that using niv is harder, or somehow not superior to using Docker is really a hot take. I am sad I ever entered this thread. EDIT2: I'll leave this here and stand by it 110% and I'll insist it proves my point: >If you can do this, with flakes, or in pure-eval mode, it's a stop-everything bug in Nix.