3 ms·

1. OP article has nothing to do with JavaScript. 2. It's not like the JS community is anti-XML, most JS libs/frameworks still use HTML/XML markup for rendering

• devwastaken 10y ago
  >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.
  • deleted 10y ago
    [deleted]
  • cocktailpeanuts 10y ago
    > 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.
• gambler 10y ago
  >1. OP article has nothing to do with JavaScript. 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).