4 ms·
> Browsers may have XML parsers built in, but XML requires APIs to work with in any meaningful way. That's fine. APIs are good. The problem with XML is that th
by porker 8y ago
> Browsers may have XML parsers built in, but XML requires APIs to work with in any meaningful way.
That's fine. APIs are good. The problem with XML is that the APIs never got any love from the end-user perspective. They are horrible to use, (seemingly) overcomplicated and the ones I've used, inconsistent.
I've seen one or two nice Python wrappers (forget names, been a long time since I worked with XML) that smoothed out the Developer Experience (DX), but that's it.
For me, this is the reason as a programmer I prefer to work with JSON, even though as a data author and maintainer I prefer XML at every level.
- cryptonector 8y agoAnd as if dealing with JSON requires no APIs. Perhaps because I use libjq, I'm spoiled? But no, I can't imagine starting from scratch and not building an API for dealing with JSON.