> Now that we've seen what happens with languages like Cue I'm not so sure anymore. Could you maybe elaborate on this point? Or point me to other resources det

> Now that we've seen what happens with languages like Cue I'm not so sure anymore. Could you maybe elaborate on this point? Or point me to other resources detailing this argument? I'm unaware of details about the cue project: i found it interesting on paper but when i never tried it as i personally consider it's useless as long as you can't validate data against an external schema (like JSON-LD or XML schemas). > The only difference would probably be slightly better error messages for incorrect type applications on builtins. Why only on built-ins though? If nix was statically typed, every package could define its own types for configuration/overrides and entire documentation could be auto-generated. I was not aware of yants, it looks great but it sounds like something that would be very useful as part of nix itself (like a nix check command). I love nix/guix as a concept but every time i've tried i've been been put off by severely-unintelligible errors due to bad typing or simple syntax errors (due to my lack of experience of what to use where and lack of documentation on expected types).