- Joined
- Oct 19, 2023
it might have shit like namespaces and there might be a bunch of weird shit around it like xslt, but if you look at only the core document format specification, it's not as horrible as a lot of programming circlejerkers say it isYes and no, there's a lot of extraneous horseshit in the spec, and you run into this behavior regularly, which is, in part, why JSON is replacing it in a lot of data serialization contexts.
this isn't xml's fault really, this is niggerlicious niggers defining different dialects of a format designed to be interoperable and not have a bunch of stupid fucking dialectsThis is a place where I have felt significant corporate pain. The MS Office and MS Visual Studio groups had their own, non-interoperable XML specifications (was working with Sharepoint 2013 at the time; Microsoft specified data queries in Sharepoint using an XML dialect called CAML) and it required weird monkey patching to make them work together. Boss hated when I'd spend time to make my life easier in the long run, which required doing things like this. He'd been basically a nocoder for a decade or two. Horrid workplace unless you know how he likes his cock sucked.
don't blame xml for microsoft's stupid mistakes because if you applied that rule for everything microsoft has fucked up badly you would quickly conclude that everything is terrible (which is true for other reasons, just not because microsoft is really good at fucking everything up)
html is the real nightmare because it follows the "be generous in what you accept" rule to its logical conclusion and shows why following that rule to its logical conclusion can be a bad ideaXML seems straightforward because most programmers worth a hoot has tried their hands at doing HTML, usually when young.