3 ms·
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
by einhverfr 10y ago
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.
- cptskippy 10y agoHmm... 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.