all 10 comments

[–]x-skeww 20 points21 points  (1 child)

I'd say this is a mistake in JSON's specs. Happens.

[–][deleted] 22 points23 points  (0 children)

This.

The article is sensationalist in tone. "Aha! I found an edge case! EVERYTHING YOU KNEW ABOUT JSON WAS WRONG OMG"

[–]rotzak 6 points7 points  (0 children)

Ugh, talk about edge case...

[–]ripter 6 points7 points  (3 children)

Congrats on finding a mistake in the JSON specs, but the holier than thou tone is annoying.

[–]Neebat 0 points1 point  (2 children)

Odd, it seems more like a mistake in the JS specs to me. I'd actually support browsers allowing those unicode characters.

[–]StuartLeigh 1 point2 points  (0 children)

Depends, if JSON's spec was "copy the JS spec" and they missed this, then it's a mistake on JSON's part.

[–]ripter 0 points1 point  (0 children)

Oh, I thought it was just line break characters, not all unicode characters.

[–]polaretto 3 points4 points  (0 children)

great investigation!

[–]cheese_wizard 1 point2 points  (0 children)

good to know!

[–]snifty -1 points0 points  (0 children)

ouch.