Re:How to Avoid Being Called a Bozo When Producing XML (2005)
by einhverfr on Sunday July 31, 2016 @11:00AM
(#12197232)
Even there, the schemas and validation are very lightweight compared to what XML can do.
As I usually say, JSON is for relatively free-form, dynamically typed languages, but if one side is uses a statically typed language, XML is probably the better choice.
Re:How to Avoid Being Called a Bozo When Producing XML (2005)
by cptskippy on Monday August 01, 2016 @09:41AM
(#12202269)
Hmm... I always tend to use XML for B2B communication or Mine-to-Theirs type RPCs. I use JSON primarily for Client-to-Server communication internally with own applications or for public APIs.
Re:How to Avoid Being Called a Bozo When Producing XML (2005)
by beagle3 on Sunday July 31, 2016 @11:06AM
(#12197267)
JSON was defined in April 2001, basically a subset of JavaScript specs from 1999.
So, JSON did exist 15 years ago, but not 16 years ago, although you have to go back 20 years if you want your statement to not just be about the name.
And yet ... how many of the decisions to use XML go back those 15 years? Hardly any.
Re:How to Avoid Being Called a Bozo When Producing XML (2005)
by cptskippy on Monday August 01, 2016 @09:51AM
(#12202335)
JSON may have been created 15 years ago but it wasn't well known or commonly used for a number of years. Yahoo! only started using it in 2005 and Google in 2006. XML had been around and in use for years prior to that and even today has a much richer toolchain.
For another, JSON didn't have validation or schemas 5 years ago.