3 ms·
Douglas Crockford usually says he discovered JSON, and subsequently named it and wrote a specification, and I think this precludes suggesting it had design goal
by inopinatus 4y ago
Douglas Crockford usually says he discovered JSON, and subsequently named it and wrote a specification, and I think this precludes suggesting it had design goals, because it wasn't an invention. More broadly, I also think this understanding of JSON's origins absolves the discoverers of its limitations, and opens the door to talking about improvements and variations.
Notwithstanding which, I too would prefer to interchange data via S-expressions.
- xbar 4y agoI don't follow your discovery/goal-less-ness argument. Why couldn't one of the things present in his discovery be readability? +1 on those S-expressions.
- inopinatus 4y agoEarly versions of JSON supported // comments. As Crockford tells the story, they were removed because folks were using them for pragma, leading to interoperability issues, and because several parser authors working in languages other than Javascript reported surprising levels of complexity when implementing comments. My point being; aspects that seem like irritating omissions now, may have been editing decisions instrumental in the overall adoption of the standard.
- Dylan16807 4y agoHe made changes that were based on design goals. He simplified a few parts, and removed comments with the explicitly stated goal of avoiding parsing directives. We can say the underlying idea of taking javascript's object syntax was a discovery, but he refined it between discovery and release.
- inopinatus 4y agoThis seems to merely be applying Saint-Exupéry's rule as an editor, which is a matter of baseline competence, and hardly seems worthy of description as a goal of any sort.