> There's no need to be rude. If you can't make your point without
> attacking people, then you need a better argument.
If you can't make your point without misusing terms to the point of
making yourself untrustworthy on that level alone, stop trying to
argue.
The "lazy programmer" axiom doesn't apply to terminology.
> "JSON" in this case just means a simple object notation using {, [,
> and :. You know that.
Nope. I have NEVER heard a knowledgeable developer use "JSON" in this
way. I consider myself a mid-level Javascript developer, so I'm always
learning both formal coding patterns and informal jargon from people
at the expert level -- but I've never heard this. Evidence, please,
for this claim that the term "JSON" is so abused by people who
provably know better.
> "JSON" is the best word available.
Give me a break.
JavaScript object literal.
As above, no knowledgeable JS dev refers to
{ name : function(args) }
as actual or informal "JSON."
> Unless you can suggest a better word to differentiate this format
> from the others (one that isn't designed to insult anyone who
> disagrees with you) stop fussing about it.
You explicitly claimed that "any browser will take" your
JSON-with-interpolated-function-return. And you firmly stated you
wanted "par with all the other JSON parsers in the world."
You're saying that, um, "JSON parser" and "JavaScript engine" are
known to be interchangeable?
Please, just... stop. The time taken here could be better spent
reading the JSON and ES-232 specs than making up false "common
knowledge."
-- S.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
