News for hackers. Stuff that matters.
Re:The Rise and Rise of JSON (2017) by ryanar on Wednesday July 22, 2020 @04:34PM (#23921270)
I read and work with JSON all the time, logs, responses, code generated from json data. The format suffers from not being readable because of the quotes issue. Especially when what you are putting in there has quotes, the amount of escaping required is ridiculous.

{"time":"2020-07-22T10:59:14.95406-04:00","message":"{\"level\":\"debug\",\"module\":\"system\",\"time\":\"2020-07-22T10:59:14.953909-04:00\",\"message\":\"Running MetricCollector.Flush()\"}"}

this is a very moderate example of what I deal with daily, all because JSON includes quotes around fields.

Re:The Rise and Rise of JSON (2017) by rileymat2 on Wednesday July 22, 2020 @04:57PM (#23921493)
It gets worse when you want to put it into a c-string and you need to escape the quotes and the slashes again.
Re:The Rise and Rise of JSON (2017) by ryanar on Wednesday July 22, 2020 @07:42PM (#23922752)
exactly, I am excited about new formats like Amazon's Ion though https://github.com/amzn/ion-js
Re:The Rise and Rise of JSON (2017) by blackrock on Thursday July 23, 2020 @05:53AM (#23925712)
They embedded a JSON string within the JSON itself.

I wonder if it would’ve been better for them to Base64 encode their message. Of course, this itself presents other problems.