Re: [xml-dev] XML vs JSON
The reason this is a thing is because JSON is being pushed into domains that it was not designed for and totally unsuited for.
Huge amounts of time and money are being spent on JSON support in domains where JSON has no business being (complex data interchange models like NIEM, UML etc) for the wrong reasons - to make developers life "easier" often at the expense of every other person that needs to interact with that data.
Ken Holman puts the finger on the issue perfectly.
On Tue, Aug 1, 2017 at 6:07 PM, John Cowan <[email protected]> wrote:
On Tue, Aug 1, 2017 at 1:54 PM, Thomas Passin <[email protected]> wrote:Many of the responses so far seem to assume that the server's output will be consumed by a web browser, and be processed with javascript. But if we're talking about "services" in general, this is far from the only case.Indeed, it's partly because JSON parsing returns an anonymous object, whereas XML parsing messes with the DOM, that JSON is easier to use for arbitrary interaction. But if you use James Clark's MicroXML parser, you can consume a stream of (Micro)XML and turn it into similarly anonymous objects.--John Cowan http://vrici.lojban.org/~cowan [email protected]BALIN FUNDINUL UZBAD KHAZADDUMUBALIN SON OF FUNDIN LORD OF KHAZAD-DUM