> Comments, trailing commas, and multiline strings. IMO, that would make it "good enough" for most use cases. Having the application parse a date from a strin

> Comments, trailing commas, and multiline strings. IMO, that would make it "good enough" for most use cases. Having the application parse a date from a string isn't too bad. And dropping quotes on keys is just a nicety. And really, trailing commas aren't strictly necessary either. But comments are absolutely necessary for a human readable configuration format. And multi-line strings are critical for any use case where you have strings that could be long. Like, say, a "description" field. As a sidenote, the absence of multi-line strings is a major frustration I have with writing JSON schemas in JSON.