casept

6 ms·

1. 31.▲
   by casept 6y ago

   This is why I prefer nix over docker for dev environments. I can just start a nix-shell and have all of my regular tooling available in addition to the environment-specific packages.
2. 32.▲
   by casept 6y ago

   Docker containers were not meant to be used that way. LXD containers on the other hand are excellent for running multiple services.
3. 33.▲
   by casept 6y ago

   NixOS exposes config options as variables you can set in your configuration.nix file. Also, external config management tools generally interact poorly with nixOS, because they assume a system which is managed imperatively.
4. 34.▲
   by casept 6y ago

   Static linking is unfortunately broken for many projects though, primarily because every C/C++ dependency has a slightly different incantation to make it work. It also doesn't address the problem of languages which expect dependen
5. 35.▲
   by casept 6y ago

   Docker kind of sucks for development though, because you need to reinstall all your devtools into the container and have to wire up your IDE to support docker. With nix, you just write a shell.nix, run nix-shell and can then use your regula
6. 36.▲
   by casept 6y ago

   It's necessary to hardcode paths in order to ensure that the exact version of a dependency is linked into the executable. Without this mechanism, nix packages would not be reproducible and self-contained. Also, the path isn't real