4 ms·

> I kinda thought the whole reason this deeply-mediocre format caught on in the first place was it was especially natural & fast to serialize/deserialize in Jav

> I kinda thought the whole reason this deeply-mediocre format caught on in the first place was it was especially natural & fast to serialize/deserialize in JavaScript, on account of being a subset of that language No, people couldn't just eval random strings, especially the ones containing potentially malicious user input. They started writing parsers like any other language, then came the global JSON.parse and .stringify per spec. I can't say for sure but I doubt JSON being a JS subset helped at all.

masklinn 3y ago
> No, people couldn't just eval random strings, especially the ones containing potentially malicious user input. hehehehehe > I can't say for sure but I doubt JSON being a JS subset helped at all. Oh it very much did, both because it Just Worked in a browser context, and because the semantics fit dynamic languages very nicely, and those were quite popular when it broke through (it was pretty much the peak of Rails' popularity).