3 ms·
You need to read between the lines and know the history. Restricting to UTF-8 and disallowing the previous allowed UT-16 and UTF-32 BOM's (which my JSON librar
by rurban 9y ago
You need to read between the lines and know the history.
Restricting to UTF-8 and disallowing the previous allowed UT-16 and UTF-32 BOM's (which my JSON library is the only one which did support that), is the most prominent change, yes.
What is troubling to me is that they now prefer relaxed RFC 7159 over strict RFC 4627. The RFC 7159 relaxed mode was a troubled update which harms security, and it should not be turned on by default.
And whilst they support now the insecure relaxed variant, they didn't clarify the still problematic points in the spec. MUST disallow duplicate keys, or MAY? It's not specified, or specified twice contradicting itself. Same for broken UTF-8 encodings. Error or warn or silence?
It's still much better than the YAML spec though. Minor nitpicks.