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.”

  • Tanoh@lemmy.world
    link
    fedilink
    arrow-up
    5
    ·
    2 days ago

    And no comments, unless you use a non-standard parser. But then you might as well use anorher format.

      • abbadon420@sh.itjust.works
        link
        fedilink
        arrow-up
        6
        ·
        2 days ago

        Lol. That works, but its hacky.

        The meaning of a “comment” is an integrated language feauture to write something that is not parsed by that language. This is just regular JSON.

          • tyler@programming.dev
            link
            fedilink
            arrow-up
            1
            ·
            1 day ago

            Now put a newline in your comment, to make it readable. Clearly you can see the problem here right? “comment2” isn’t a comment. It’s a key with a value. Numbering them doesn’t actually fix anything, in fact it makes it much much harder to maintain.

      • bleistift2@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 days ago

        This only works if the software that consumes the JSON doesn’t validate it or ignores keys it doesn’t recognize (which is bad, IMHO).