note 91711 deleted from function.json-decode by danbrown

Note Submitter: gruvin at gmail dot com ---- [imho] One could argue that, since JavaScript and indeed X/D/HTML are all implemented in a "forgiving" fashion, and thus going to be used in a "flexible" fashion by pretty well all in sundry, that any functions designed to work with I/O to/from those technologies should themselves be written in "forgiving" fashion, or risk rendering themselves quite pointless. I for one see no reason to futz with a strictly RFC compliant function when the simple fact is that nearly nobody writes RFC compliant JSON, preferring instead to use common-practice JavaScript syntax, which, besides looking much neater, DOES work just fine "everywhere else". Frankly, if the RFC is so important (and of course it is), then I say it is currently mismatched with reality and should be reviewed in kind. Meanwhile, should not intelligent, forward-thinking developers, endeavor to take up the slack, just as we always have in the past? What is so evil about being "RFC-compliant-plus-quirks", like most everything else in Cyberland? [/imho] Keep up the good work! We DO appreciate all your efforts out here you know. :D (No, I don't work for m$-ie and would never suggest the developers go quite that far! :P )