4 ms·
Is that a fair comparison? FTA: > Even if you can (ideally) pull a path from a cache instead of building it, you still have to pay Nix’s evaluation tax in det
by nothrabannosir 2y ago
Is that a fair comparison?
FTA:
> Even if you can (ideally) pull a path from a cache instead of building it, you still have to pay Nix’s evaluation tax in determining the derivation’s store path in the first place. [...] Fortunately, FlakeHub now offers an elegant solution to this problem: resolved store paths.
If I may paraphrase:
> [fundamental problem with Nix] -> [proprietary solution].
Cachix and nixbuild feel like they're solving something at a different layer. They fit into the existing Nix ecosystem (binary cache, builders) and just provide a hosted version of an existing concept. They don't change anything fundamental about Nix.
Maybe a better comparison would be devenv?
- _cenw 2y agoI don't object to the product, I object to DetSys moving CppNix into more of an de-facto open core product[1]. This is just a symptom. DetSys contributes the majority of the code that actually gets prioritized and merged (because the maintainer is a DetSys employee), but asking them to build better caching mechanisms into CppNix (which, to be clear, I never asked, that's just Luc's strawman of me) instead of their proprietary product is suddenly "asking Eelco to work for free". [1]: https://discourse.nixos.org/t/announcing-determinate-nix/54709/ https://discourse.nixos.org/t/announcing-determinate-nix/547...