For some reason, the performance doesn't seem that clear cut.<p>For instance, I get the following on Chrome, running it a few times:
(Doing 100,000 parses of a small JSON string)<p>JSON: (1653ms) vs eval: (206ms)<p>Firefox the two are about even (650ms). Safari is also pretty much identical (250ms).<p>Surprising that the Chrome JSON parse is so much slower than eval.<p>Do you have any performance figures for JSON parsing?<p>So you have JSON.parse which is the same, if not slower (Chrome) than using eval. Having to include extra unnecessary characters costs you bandwidth, but you do get the slightly better security from JSON, although that can be done with a quick regexp beforehand.<p>{foo:1} <i>should</i> be valid dammit. It tells us exactly all we need to know, with 0 ambiguity.<p>just my 2c.