15
The lost art of XML — mmagueta (marcosmagueta.com)
submitted 9 months ago by to c/webdev@programming.dev
4 comments fedilink hide all child comments
 

There exists a peculiar amnesia in software engineering regarding XML. Mention it in most circles and you will receive knowing smiles, dismissive waves, the sort of patronizing acknowledgment reserved for technologies deemed passé. "Oh, XML," they say, as if the very syllables carry the weight of obsolescence. "We use JSON now. Much cleaner."

you are viewing a single comment's thread
view the rest of the comments
[–] 7 points 9 months ago (2 children)

XML lost because it pretended to be human readable but it's actually a soup of punctuation, and pretended to be good for machines but is heavy to parse and transmit.

If there was an explanation for why XML lost to the likes of Avro and Thrift I didn't spot it.

I do think it's a shame that the only real alternative to JSON is the much more complex yaml, but I'll take it for most purposes.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] 4 points 9 months ago

    It wasn't even just that. In the companies I worked, it seemed like nobody other than me understood how to escape things for XML. I couldn't even convince them to just use the right libraries/functions that auto-escape and parse things properly. They keep deciding they were smart enough to do it by hand. And it always ended up biting them.

    JSON, like Javascript (vs C++ or Java) is a lot more forgiving. It either works or it doesn't, and the values are just strings or numbers. And some people even do the numbers as strings.

  • permalink
  • fedilink
  • source
  • parent