> has been able to explain a reasonable and concrete way to tell what any given variable is within a Nix source file That’s the problem with the anemic and ad

> has been able to explain a reasonable and concrete way to tell what any given variable is within a Nix source file That’s the problem with the anemic and ad hoc libraries nixpkgs uses, not the language. There is a magic buildWhateverXPackage function that needs some magic attributes and you are done. The problem is that there is no interface to aid in how that should be used - but it is the same way in JavaScript as well. Also, you are writing a description of something, it won’t be a traditional program with an event loop or whatnot - here lazyness does make sense.