3 ms·
"it is the javascript object notation." Except it's not, which is part of the reason this sub thread started. JSON encoded numbers are not IEEE754 floats eithe
by polemic 13y ago
"it is the javascript object notation."
Except it's not, which is part of the reason this sub thread started. JSON encoded numbers are not IEEE754 floats either. And JSONP is purely a convenient hack around browser security issues only, again it has noting to do with JSON as a format.
You can argue the specifics,, but you miss the point that the claim that "JSON is JavaScript" is false and leads to tricky edge cases when the assumption breaks down.
- mcv 13y ago> And JSONP is purely a convenient hack around browser security issues only, again it has noting to do with JSON as a format. It gets around those browser security issues by having the JSON wrapped in a function call and interpreted as javascript. I've never heard of a server converting all the values for JSONP. There are absolutely edge cases, and those are important to note, exactly because outside those edge cases JSON is valid javascript. Claiming that they are totally completely unrelated (like javascript and Java) is false.