eww, UTF-16 surrogate pairs. Die, die, die, you scourge. (Yes, I've been working with the win32 api lately, which was designed for UCS2/UTF-16).
when has 16 bit anything been a good idea, really. TCP port ranges, looking at you too.
101–110 of 199 posts
eww, UTF-16 surrogate pairs. Die, die, die, you scourge. (Yes, I've been working with the win32 api lately, which was designed for UCS2/UTF-16).
when has 16 bit anything been a good idea, really. TCP port ranges, looking at you too.
Earlier quoted context omitted.
~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?
This is based on my experience at UPS which used a single machine using IE6 and some form of web app to control start up and shut down procedures, or something to that effect. It had no Internet connection, only LAN I believe.
I did ask myself this question too and it does seem peculiar. After some thought, my only guess is the above!
Earlier quoted context omitted.
> 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.
Earlier quoted context omitted.
Not really... just add a "comment" key and then ignore it when processing.
Yes, that solution OBVIOUSLY removes the need to spend an extra minute adding comments to the spec. Also, I hope, trailing commas and binary types.
Earlier quoted context omitted.
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.
Earlier quoted context omitted.
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?
Earlier quoted context omitted.
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?
Consider it an "anti-'people who take licensing seriously' license".
Earlier quoted context omitted.
I was crossing my fingers for that too. I create JSON files a lot. It's annoying when I'm _reordering_ elements separated by newlines. It's annoying when I'm generating JSON files and I have to code in a special case to skip the comma. It breaks the consistency that I just desire as a programmer.
Why do you manually code json?
Earlier quoted context omitted.
I was crossing my fingers for that too. I create JSON files a lot. It's annoying when I'm _reordering_ elements separated by newlines. It's annoying when I'm generating JSON files and I have to code in a special case to skip the comma. It breaks the consistency that I just desire as a programmer.
Why do you manually code json?