Re:How we turned JSON into a full programming language
by wircho on Saturday June 20, 2015 @09:11PM
(#9751681)
It's more straightforward than this. Think of it as a more comprehensive Yahoo Pipes or IFTTT, where the nice graphical interface is not yet released publicly. So for now developers can just write the raw JSON. Yes, a LISP interpreter would have done that job (as would a library written in some other programming language). However you are not allowed to download code into an iOS app (precisely for security reasons), and so we're downloading items from a predefined documented list of macros. This simplicity, in turn, makes creating a graphical interface a lot easier, without sacrificing the fact that the structure is as flexible as a functional programming language.
[ Parent
| on HN ]
Re:How we turned JSON into a full programming language
by pablovidal85 on Sunday June 21, 2015 @05:55AM
(#9752819)
So your language is not turing complete?
Re:How we turned JSON into a full programming language
by wircho on Sunday June 21, 2015 @09:00AM
(#9753246)
I would say it's not, since it lacks conditional branching, although one could argue that you can simulate a Turing complete system on a Relevant card by having a user indefinitely tap on a button that refreshes it at the next state.
Re:How we turned JSON into a full programming language
by pablovidal85 on Sunday June 21, 2015 @04:11PM
(#9754809)
Understood, I stand corrected. Anyway, I would have used some kind of non-turing complete stack language.