JSON is the new XML. Except XML was actually designed to have semantics, while similar attempts in JSON are just hacks.<p>In general, JavaScript is becoming the new J2EE. Ambitious ideas, clueless implementations, insane complexity.
So why JSON of all things? When I reached the "write a full declarative program in JSON" section I was internally screaming "but s-expressions!"
That's nothing. I can write a chess engine using nothing more than the Latin alphabet, Arabic numerals, and a couple punctuation characters. All you have to do is compose these building blocks in the right way, and gcc will take care of the rest.
I've seen so many projects like this over the years that claim that they're the one that will allow for true cross platform app development, and they've developed a simple abstraction for doing so.<p>I've never seen any succeed at anything more than the most basic apps.<p>I put more stock in projects like Xamarin or MOE (and even they aren't perfect).
A heads up for anyone wondering if this can do anything "real" on the phone (such as, you know, take a picture or access the memory card):<p><a href="https://forum.jasonette.com/t/media-in-android-port/79/2" rel="nofollow">https://forum.jasonette.com/t/media-in-android-port/79/2</a><p>Short answer: <i>Sort of</i> (on iOS) and <i>No, not yet</i> (on Android)
The framework and approach described might be useful in some cases, but... you still need to understand CSS, HTML, and... pretty much everything about webfrontendism to meaningfully design and "build" such an app, of course (even if you do manage to cram all that metadata into a single JSON file).<p>So it's a bullshit title, basically.