| 20 Dec 2025 |
 bandithedoge | real | 19:49:12 |
 raitobezarius | In reply to @cyclopentane:aidoskyneen.eu
another missing puzzle piece imo: currently, Nix treats the eval process and the build process as two conceptually separate things. But afaict there's nothing stopping us from treating the evaluation of, say, a flake as a derivation too - that derivation would have the flake source, its dependencies and nix as inputs, and output a .drv file I also have this in my mind and I'd like it to happen | 23:47:22 |
| 21 Dec 2025 |
 SomeoneSerge (back on matrix) | It's more like aterm drv and nixlang are two different languages and both are by default applicative, with ifd making nixlang monadic and dyndrv making aterm monadic. But also I've never managed to read "a la carte" as anything more than a bunch of handwavy metaphors when applied to nix, so idk, maybe I'm too slow for this | 01:17:51 |
 jakehamilton | In reply to @sofiedotcafe:matrix.org
@jakehamilton:auxolotl.org do you have an example of Nilla but with agenix or similar? Ah I don't, I am not a fan of agenix and other existing secret solutions due to the manual work required :( | 01:19:08 |
 Acid Bong | In reply to @sofiedotcafe:matrix.org
@jakehamilton:auxolotl.org do you have an example of Nilla but with agenix or similar? Nilla is just a Nix entry point system, like flakes, while Agenix and such live within NixOS | 03:34:10 |
