>> "Again, though, you should probably be modifying your busted server-side code to stop sending malformed JSON!"<p>I still think it was a silly mistake to impose a 'must be enclosed in quotes' rule for JSON parsing in js.<p>Those quotes are just wasted extra bytes. Needless.<p>Yeah sure, you can argue that someone silly will use a reserved word, like {new:"hello"}.
But I don't think that's a good enough reason to waste more bandwidth+time for those that know what they're doing.
Came up at least once before, but no discussion there:<p><a href="http://news.ycombinator.com/item?id=1054409" rel="nofollow">http://news.ycombinator.com/item?id=1054409</a>
I had a problem with this today when upgrading from jQuery 1.3.2 to 1.4. The AJAX functions worked fine in Firefox, were returning "parseerror" in Safari because there was a non-UTF-8 character in the JSON response.