JSON is a format directly derived from JavaScript. The affinity for using JSON for things that have nothing to do with object serialization or simple data structures is characteristic of JS mentality.
>2. It's not like the JS community is anti-XML, most JS libs/frameworks still use HTML/XML markup for rendering.
Of course JS community is anti-XML. They don't use XML even when it makes sense to do so. And they use HTML only as a rendering layer, completely ignoring its other use (e.g. semantic document format).
>It's not like the JS community is anti-XML, most JS libs/frameworks still use HTML/XML markup for rendering.
Its pretty anti-XML outside of node. Pure-js solutions for xml are not as great as built in features other languages provide, while JS only natively does JSON.
>generalisations around 'clueless implementations, insane complexity' don't make a lot of sense.
When you are creating languages that compile to JS and adding entire markup ontop of it along with literally hundreds of dependencies in any average project, JS has plenty of insane complexity.
> When you are creating languages that compile to JS and adding entire markup ontop of it along with literally hundreds of dependencies in any average project, JS has plenty of insane complexity.
Like parent said, this project doesn't compile to JS. It's simply a JSON to native mapping.
Except XML has no evaluation rules and no semantics. It allows you to build languages that can be processed by third-party tools, which then give a precise meaning: for example, SVG expressions are written in XML, but the meaning is not expressed in XML.
In general, JavaScript is becoming the new J2EE. Ambitious ideas, clueless implementations, insane complexity.