News for hackers. Stuff that matters.
Re:Show HN: JSON5 — modern JSON by zacharyvoase on Sunday May 27, 2012 @11:41PM (#4031820)
Can I ask why YAML wasn't good enough?
Re:Show HN: JSON5 — modern JSON by chc on Sunday May 27, 2012 @11:49PM (#4031842)
My thoughts exactly. YAML is a superset of JSON that already has all this stuff and more.
Re:Show HN: JSON5 — modern JSON by aseemk on Monday May 28, 2012 @12:13AM (#4031901)
I actually had no idea that YAML is a superset of JSON. Thanks! I'll look into it.
Re:Show HN: JSON5 — modern JSON by silentbicycle on Monday May 28, 2012 @01:05AM (#4032028)
For the same reason sexps weren't good enough, apparently.
Re:Show HN: JSON5 — modern JSON by erikpukinskis on Sunday May 27, 2012 @11:55PM (#4031855)
Partly because JSON has the lovely feature of being able to just eval() it into an object in browsers.
Re:Show HN: JSON5 — modern JSON by chc on Monday May 28, 2012 @12:13AM (#4031898)
That's not really a lovely feature in this day and age. If anything it's an unfortunate artifact, as the right way to deserialize JSON is JSON.parse().
Re:Show HN: JSON5 — modern JSON by alcuadrado on Monday May 28, 2012 @12:00AM (#4031863)
That's not the right way to parse JSON, it's really insecure
Re:Show HN: JSON5 — modern JSON by Too on Monday May 28, 2012 @12:56AM (#4032001)
And slow, JSON.parse is magnitudes faster than using user-javascript to parse it yourself.