11–20 of 120 posts
There are so many cool things you can do with JSON. I just created a boolean logical statement builder on a web page by using free form open and close parenthesis, and and/or radio buttons. A little regex to change the parenthesis into square brackets, then an eval(), and I can walk the whole statement recursively.
JSON is popular because there is a straightforward mapping from JSON to native types in many programming languages.
I am actually using such isomorphisms in my current porting project. I'm literally getting a couple of orders of magnitude more productivity out of this over porting by hand.
Also note: less syntax makes this easier.
Earlier quoted context omitted.
Sorry we were late to the party, guys, we just got so wrapped up in writing software that people actually use.
... while the lispers where still counting the closing parens needed to finally get their code running SCNR
There seems to be something inherent in us that feels the need to turn our tools into our religion. It's not terribly productive.
This begs the question, "Why would you do something that convoluted?" Well, you can ask the same of the XML examples, and the answer probably boils down to requirements (or incompetence?).
Earlier quoted context omitted.
... while the lispers where still counting the closing parens needed to finally get their code running SCNR
Only the ones too clueless to use Emacs or another editor that does it for you.
There are so many cool things you can do with JSON. I just created a boolean logical statement builder on a web page by using free form open and close parenthesis, and and/or radio buttons. A little regex to change the parenthesis into square brackets, then an eval(), and I can walk the whole statement recursively.
eval() strikes me as a dangerous thing, security-wise.
Isn't it dangerous to eval()? Suppose someone put some malicious code in the JSON data?
JSON is popular because there is a straightforward mapping from JSON to native types in many programming languages.