|
|
|
|
|
by tracker1
3467 days ago
|
|
But that's not concrete without another definition in place <foo yo="true">
<bar>1</bar>
<value>Hello</value>
</foo>
Could represent the same object structure, for example. JSON is a pretty clean mapping to objects/properties/arrays, with less chance of confusion, or alternate interpretations. |
|
Whether something is inside an element or is a property of said element has important semantical meaning. But not just that, with XML you can implicitly represent ordering, whitespace and type information with much less boilerplate.
So the argument for JSON is basically boils down to: "Javascript has horrible type support and doesn't support OOP. JSON models that experience better."