> This is the major problem with most comparisons of config file formats: the actual semantic domain of a config file format is extremely limited [ ... ]
So, why not use Scheme ?
So, why not use Scheme ?
Personally I think the right answer for configuration files is to define them in terms of a generic object model. A program could even support multiple formats (TOML+JSON+YAML). If a user dislikes all the supported formats or the file is generated with something like NixOS, it can be handled with straightforward conversion.
I invite you to check out Symfony where you configure your app using yaml, attributes in code, code itself, or a mix of all the above.
You will cry.
(Don't shoot the messenger, I've done my fair share of scheme. I've also done a lot of thinking about why some people are so turned off from the syntax, and it's certainly not that the opening parenthesis is in a slightly different place on the prefix function calls)