Why 404.
ECMA-404: The JSON Data Interchange Format [pdf]
81–90 of 199 posts
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#82Earlier quoted context omitted.
https://plus.google.com/118095276221607585885/posts/RK8qyGVa...
That's pretty laughable. What exactly prevents people from putting parsing directives in a special object key or list entry at the beginning of the file?
that would be valid JSON, so it's not a problem. Standard tools can still parse it and reliably turn it into native objects. The same is not at all true when comments exist. People will start putting /* @annotations */ that can only be ready by certain tools which breaks the whole point of JSON - it's a data interchange format.
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#83Earlier quoted context omitted.
If I could down-vote this lazy, drive-by, language bashing I would. Back up 'so messed up' or keep comments like this to yourself, they don't help the discussion.
It is a terrible language, though. That's common knowledge. It is, however, wrong to say it's terrible because of laziness.
I really don't think it's fair to say it's a terrible language. It does have some terrible, horrible parts. But it also has some wonderful, awe-inspiring, mind-blowing parts. It's just not a MOR language - you have extreme lows and awesome highs.
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#84Earlier quoted context omitted.
> you would break json parsing in all old version of IE Why do people still care about old versions of IE?
~22% of China still uses IE6: http://www.ie6countdown.com/ Developing nations have a tendency to not use the latest and greatest. If reaching them is important for you/your product then you have to keep tracking this stuff.
> Developing nations have a tendency to not use the latest and greatest.
Attention developing nations: Chromium and Firefox are completely foss. No excuse, unless you don't have an internet connection.
In which case, what do you need a web browser for?
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#85Earlier quoted context omitted.
Trailing commas would make the problem worse! If you allow trailing commas then you would break json parsing in all old version of IE. The unicode line ending problem is more subtle. I have seen people write code like (mix javascript and some templating): var prefs = ; ... The above code looks okay, but if the json is just spec conforming, then you are exposed to a potential XSS attack. Most people that write json en…
> If you allow trailing commas then you would break json parsing in all old version of IE. No, you would break the evaluation of json as javascript in old versions of IE. Use a real parser already.
I do use a real parser, but it is not possible for JSON-P.
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#86Several comments mention the "Software shall be used for Good, not Evil" licensing issue in the JSON code from json.org. The original json.js file from json.org had this copyright and license: Copyright (c) 2005 JSON.org Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, includi…
You mean Douglas Crockford broke down and gave into the "pro-evil fanatics"? For context, after Mr. Crockford gave IBM permission to use the license without the clause a few open source projects (mine included), also asked, and Mr. Crockford's response was a bit over the top- > I released to free use for all with the only condition that it not be used for evil. If that is unacceptable to you, then you may not use it.…
"Pro-evil"? Wow. Is it so hard for people to realise the problem is the potential interpretation of "evil" is very open ended?
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#87Earlier quoted context omitted.
It is a terrible language, though. That's common knowledge. It is, however, wrong to say it's terrible because of laziness.
I really don't think it's fair to say it's a terrible language. It does have some terrible, horrible parts. But it also has some wonderful, awe-inspiring, mind-blowing parts. It's just not a MOR language - you have extreme lows and awesome highs.
"wonderful, awe-inspiring, mind-blowing parts"
Honest question: Such as?
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#88Earlier quoted context omitted.
This sucks, because it limits the usability of JSON. It should interfere with its being a serialization and interchange format, but for configuration files anything without comments is useless.
https://plus.google.com/118095276221607585885/posts/RK8qyGVa...
That's such a terrible response. "Use JSON, but then use another parser first." Sorta defeats the purpose.
The reasoning is also incredibly short-sighted.
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#89So the standard says a valid JSON text complies to the JSON value grammar. So a valid JSON text can be just one JSON value, like a number or true or false.. however JSON linters always say they expect a { or [ ... who is right?
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#90Several comments mention the "Software shall be used for Good, not Evil" licensing issue in the JSON code from json.org. The original json.js file from json.org had this copyright and license: Copyright (c) 2005 JSON.org Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, includi…
That's great news. It has been a major inconvenience to remember to use XML in all of my evil applications.
I switched a few of mine to JSON but the clients complained that this undermined the final deliverable. I was forced to switch back.