4 ms·
I think XML gets a bad rep for a similar reason that CSV gets a bad rep. i.e. there is a wide variance of what “passes” for XML, and two systems that profess t
by gen220 5y ago
I think XML gets a bad rep for a similar reason that CSV gets a bad rep.
i.e. there is a wide variance of what “passes” for XML, and two systems that profess to “speak” XML often speak mutually incomprehensible dialects.
I think each of your valid complaints about JSON extend to XML, for example. Totally agreed that XML gets an especially bad rep because most xml parsing/generating libraries in popular programming languages are frustrating.
- dathinab 5y ago> i.e. there is a wide variance of what “passes” for XML not really, it's standardized. what differs is how it's used, i.e. a top of most serialization formats there is another implicit often overlooked serialization layer which roughly maps domain logic to the structures the serialization format supports. The problem with XML is similar to that of XMPP, to many features and variations, nobs to twist, things to easily subtle get wrong, etc. Also string content encoding is terrifying in XML as it overlaps string content and string formatted control structures and pretty printing in a messy way. (Like imagine pretty printing _inside_ of a json string without clear separation of weather or not a newline is content or formatting.)
- TylerE 5y agoThen you hit the hell of having to interact with some system (almost always written in Java) that's using some 20 year old SAX parser that barfs if the tags aren't in the exact order it expects.