3 ms·
I say just use JSON. Everyone knows it already and it's good enough. Use a parser in your app that allows comments and trailing commas like vscode does.
by markmark 7y ago
I say just use JSON. Everyone knows it already and it's good enough. Use a parser in your app that allows comments and trailing commas like vscode does.
- dagenix 7y agoThat's not JSON anymore, that's some custom format that's JSON inspired.
- deleted 7y ago[deleted]
- skybrian 7y agoYep. Some kind of JSON++ is where we're headed. Hopefully we can agree on a new standard someday? (No, not YAML.)
- tln 7y agoJSON5.org would be nice :)
- wwright 7y agoIf JSON did support this (and multiline strings), I think it’s unlikely anyone would reach for anything else.
- markmark 7y agoCool. It doesn't matter.
- deleted 7y ago[deleted]
- jaredklewis 7y agoI dislike json with comments or trailing commas as even if your parser can handle them, it surprises many text editors. Aside from lack of comments, the other major thing that can sometime make json a bad config choice is lack of multi-line strings.
- sigzero 7y agoJSON is for data. Not documents. Not config files. I don't agree with any "add this to JSON" comments. It's fine just as it is....for data.
- dragonwriter 7y agoConfig files are data about program configuration. So “for data” and “not config files” don't go well together.
- h1d 7y agoIt's called JSON5. Don't bend JSON to confuse parsers. https://json5.org/ https://json5.org/