3 ms·
The frustration of XML can be divided into two parts: 1. The frustrating infrastructure build around it, such as SOAP which is anything but simple 2. The verb
by true_religion 16y ago
The frustration of XML can be divided into two parts:
1. The frustrating infrastructure build around it, such as SOAP which is anything but simple
2. The verbosity of the protocol itself which frustrates human readability which supposedly is a key feature of XML
If we use JSON and avoid the infrastructure mistakes of XML (e.g. requiring huge amounts of boilerplate for RPC calls), then I think the native readability of JSON makes it a far better choice for serialization protocol than XML.
- thwarted 16y agoYeah, that's great, but my point was that HTTP+JSON solves the easiest part, not the part that actually needs to be done: creating an agreed upon format for the content being serialized (via JSON) and transported (via HTTP). When that was attempted with XML, it ended up with multiple query methods, multiple schemas, new and obscure transport wrappers (SOAP over SMTP, for example). Maybe we can avoid a Second System Effect now going forward... if XML was the Second System.