3 ms·
You can only work with what something is. Not with what it might be, one fine day.
by TheOtherHobbes 5y ago
You can only work with what something is. Not with what it might be, one fine day.
- Athas 5y agoSure, but e.g. the documentation problems with Nix don't prevent you from working with it. While the problems make it less smooth and productive than it otherwise might have been, it might already be better than legacy systems for you. In particular, Nix can be used in a non-invasive add-on manner on ordinary distributions. We have it installed on RHEL servers at work, where it is used exclusively as a build system and for "userspace programs" (not in the kernel sense, but in the sense of programs that are not core to the functioning of the system).
- dmitriid 5y ago> Sure, but e.g. the documentation problems with Nix don't prevent you from working with it In a world where there are thousands of things for me to learn (many of them with poor documentation), Nix is just one such thing. The question is, do I care about its purported benefits, and sink my time and effort into it, or should I sink time and effort into learning Unreal Engine, playing Rimworld, or going for a walk? So far, for me (and most of the world) the last three (and the rest of the thousands of things) win over Nix.