5 ms·
I always meant to use hjson somewhere, but never managed to. YAML is so complicated, and JSON is almost fine, except for: no comments, no multiline strings. Quo
by ianbicking 8y ago
I always meant to use hjson somewhere, but never managed to. YAML is so complicated, and JSON is almost fine, except for: no comments, no multiline strings. Quoting keys is tedious but not terrible. Personally I don't mind quoting string values at all.
There are places with slightly relaxed JSON, like JSON + comments (e.g. https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Web...). But it's often not well documented, and because these relaxations lack a name there's no commonly accepted set of relaxations.
But I guess we should just accept YAML, as it seems to be the standard-that-isn't-json.
- bosaisi 8y agoTry TOML. It's like a better YAML, and seems to be getting some good adoption.
- MrTonyD 8y agoAgree completely. I usually use YAML just so I can document my work using comments. If they added "heredoc" and comments, I think that I would be happy with JSON forever.
- geezerjay 8y ago> no multiline strings I thought that the JSON way of implementing multiline strings was through an array of strings.