> Optional key quotes
Why are they optional? Why not just make them mandatory? So I don't need to guess which chars need quotes.
Edit: What most languages also lack: semantics on de-serialization. In the best case, I want to preserve formatting and stuff when the config is changed/re-committed programmatically.
Because it's supposed to be pleasant for humans and quoting keys is the least pleasant part of jsom config files.
What's so unpleasant about quoting a key?
Two extra characters per rep, each involving a "shift", and it's furthermore an eyesore to read
How is it that the comments on this post seem to consist 100% of people who think JSON is the perfect language and that any deviation from it is an unnecessary complexity? Use JSON for configuration for literally 5 minutes and you will get annoyed at quoting keys, lacking comments, escaping long strings, and juggling commas. MAML is almost exactly what I'd come up with (although I wouldn't have made commas optional, that feels weird.)
> Two extra characters per rep, each involving a "shift"
You'd expect text editors to do this automatically; I'll admit, I don't think mine does.
> and it's furthermore an eyesore to read
We'll have to disagree on that one because I think it looks a lot nicer. I always preferred quoted attributes in html too.
> How is it that the comments on this post seem to consist 100% of people who think JSON is the perfect language
I'm sure you intended that as hyperbole. JSON isn't perfect, but it's got a lot going for it, not least ubiquity.
> Use JSON for configuration for literally 5 minutes and you will get annoyed at quoting keys, lacking comments, escaping long strings, and juggling commas.
I've used JSON for configuration loads and haven't faced these issues. I'm not denying your experience, I just want to understand it.