he 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
I 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.
But 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 :)
Comments
he 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
I 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.
But 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 :)