Earlier quoted context omitted.
> And that’s just a first cut; it could be made much nicer. This is exactly the problem with S-expressions. No-one is willing to define what "good enough" looks like and create a fixed, reusable standard for how you represent these things. Instead everyone hand-rolls their own, subtly incompatible variant.
Whatever is the final evaluator gets to define what is required. Beyond that, give your users the power to do it their way. Or they will find a way to get it themselves.
Which is completely useless, because it means everyone will do it differently.
> Beyond that, give your users the power to do it their way. Or they will find a way to get it themselves.
Users put value on having a standard set of scaffolding. That's why these standardised config formats have succeeded.