4 ms·

Can you give an example of what you have tried to do in Nix that you couldn't do well due to lack of power? I imagine it is something rather fancy since for mos

Can you give an example of what you have tried to do in Nix that you couldn't do well due to lack of power? I imagine it is something rather fancy since for most configuration tasks Nix is significantly more powerful than other config file languages. Number 2 sounds like a legit bug rather than an inherent problem with the design. If you haven't already maybe you can file an issue on Github and it could get the timeouts to apply correctly.

danharaj 11y ago
Hm, i don't think i have a specific example of the first issue that isn't under NDA. In the abstract, "higher order" derivations, that is derivations that produce other derivations which in turn get built are a bit cumbersome to work with. Nix is perfectly capable of expressing complex dependencies which just invites a person to push it to its limits. The limits are purely practical. You can go as far with nix as you are patient with working in a barebones language. Number 2 is probably a bug, yea. It's certainly not a design flaw. It's just a wart. Unfortunately, even though nix has a strong community of great contributors, it's a very ambitious project and so warts and rough edges are part and parcel of the nix experience.