| 11 Jul 2023 |
 toonn | Has any profiling been done? I'd be interested to see which parts of Nixpkgs a typical system build spends most time in. | 11:20:30 |
 raitobezarius | In reply to @profpatsch:augsburg.one
roberthensing: I don’t think it’s any question I think you are forgetting you are discussing this with the person who works actively on NixOS modules and has ideas to make it fast… | 11:31:33 |
 @profpatsch:augsburg.one | raitobezarius: It’s fundamentally impossible to make it fast as far as I understand, but I’d love if it were otherwise | 12:27:34 |
| @profpatsch:augsburg.one | If you can get it to work without having to strictly evaluate all options first, then you might be able to | 12:28:15 |
| @profpatsch:augsburg.one | but then you have something that’s not the nixos module system anymore, because the semantics is different | 12:28:36 |
 nbp | It would be possible to make NixOS module use less memory and potentially be faster … by implementing it in C++.
But one must understand that the module system, while not evolving frequently is still evolving. And from my point of view, of someone who never managed to get anything large accepted in Nix source code, this is a not an option. | 12:30:54 |
 infinisil | It could be implemented as a Nix plugin | 12:31:50 |
| nbp | Not mentioning the fact that evolution would be restricted to evolution of the Nix binary. | 12:31:54 |
