3 ms·
You ditched NixOS for the very reason it was created. Not being able to run binaries with missing libraries is a feature. The idea is to make you aware of your
by max-privatevoid 2y ago
You ditched NixOS for the very reason it was created. Not being able to run binaries with missing libraries is a feature. The idea is to make you aware of your implicit dependencies, and to force you to make them explicit.
This makes me wonder if you were subjected to false advertising.
- sandreas 2y agoMaybe. I was drawn in by the reproducable setup routine that can't break the existing system. I didn't think too mich about how it is achieved.
- mingus88 2y agoAdvertising in the Nix space is wild. I first learned about it in the realm of reproducible builds as well, which feels more like a “nix the language” feature This led me to install nixos which is really kind of an output of that design, a distribution built from nixpgks. There are some rough spots that make it hard for a daily driver. That distro is a bit much for my needs and I have retreated back to a home-manager cross platform setup for my arch/debian/macos systems, and it turns out the entire reason I started looking at Nix (builds) went nowhere Getting adoption for Nix builds at work or with my OSS projects is has been hard. Docker is everywhere and easy, while Nix feels like a fractured and poorly documented ecosystem.