3 ms·
I completely disagree with this. JSON is a spec. Server-side code needs to support that spec. Adding extra eval() to support bad data formats hurts client perfo
by geuis 17y ago
I completely disagree with this. JSON is a spec. Server-side code needs to support that spec. Adding extra eval() to support bad data formats hurts client performance and adds needless complexity. And extra quotes does not add a lot of data overhead. Especially compared to transmitting XML over the wire
- daleharvey 17y agohe was mostly saying the specs (crockfords) decision was wrong, not jquerys to support it. I dont really agree, naunces like reserved words causing bugs are major irritations and ill happily put up with a few extra bytes to never deal with them
- snorkel 17y agoI don't like it. I should have a choice whether to use quotes or not, and let me suffer the consequences. I don't like API's forcing "best practices" on me. The quotes add crappy visual noise and extra bytes.
- almost 17y agoBut it's not an API, it's a data format, very different things! Supporting both just means there's two ways to say the same thing and every single parsing library has to have that extra case and the spec is just that little bit longer. I'll take the extra couple of bytes thanks :)
- axod 17y ago>> "hurts client performance" Please cite some numbers. JSON.parse is not faster than eval in my tests.