3 ms·
Why not just use YAML, which accomplishes effectively the same goals, and already has a decent amount of traction? In general I use YAML for human-edited confi
by dheera 5y ago
Why not just use YAML, which accomplishes effectively the same goals, and already has a decent amount of traction?
In general I use YAML for human-edited configuration files, because they generate clean diffs, and JSON for machine-to-machine communication, because of the wealth of obscenely optimized parsnips for every language.
- nerdponx 5y agoI don't think YAML accomplishes the same goals. I like YAML, and I think people hate on it more than it deserves (at least, in its current form). And yes, you can stream YAML documents by concatenating them with document separators. But ND-JSON/JSONLines/RFC-7464 is mostly a machine-to-machine format anyway. Maybe we should be able to customize the delimiter? The media type "application/stream+json; separator=\n" would be JSONLines/ND-JSON, "application/stream+json; separator=\x1E" would be RFC 7464, "application/stream+json; separator=\n...\n" would theoretically be valid YAML, etc.