I am very excited to watch this new space unfold. Its a huge hole in platform engineering. We need a lot of config but there often arent robust enough config languages so people end up resorting to using Turing complete languages and thats just lighting a fuse for your future self.<p>Im really excited about cuelang what is everyone else keeping an eye on?
Every time I see Nickel, I get teleported back to my days unraveling thousands of lines of Nix code in a company that used it to configure everything. I know they are trying to improve the situation, but I really don't see how this doesn't encourage the same behavior of over-engineering configuration.
> JSON data model: records (objects), arrays, booleans, numbers and strings<p>Is this the JSON data model? There are places I’ve seen this fall apart: very large and very small numbers, nulls, empty objects / arrays. How confident are you that every participant in your data interchange handles all these cases the same way? I’m suspicious of libraries that assume only they will handle your JSON.<p>Edit: just remembered another one. I had to deal with the fallout from a JSON serializer that dropped leading zeros from floating point numbers smaller than one, to save space.
How could you name a language after an element and then not use its chemical symbol as the file extension?? (Yes I know NCL means "Nickel configuration language" and can be pronounced like Nickel, but come on)