• it_depends_man@lemmy.world
    link
    fedilink
    Deutsch
    arrow-up
    1
    ·
    2 months ago

    It is very cool, specifically as a human readable mark down / data format.

    The fact that you can make anything a tag and it’s going to be valid and you can nest stuff, is amazing.

    But with a niche use case.

    Clearly the tags waste space if you’re actually saving them all the time.

    Good format to compress though…

    • Caveman@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      2 months ago

      I don’t mind xml as long as I don’t have to read or write it. The only real thing I hate about xml is that an array of one object can mistaken for a property of the parent instead of a list

    • ByteJunk@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      2 months ago

      I disagree, with a passion.

      It is soooo cluttered, so much useless redundant tags everywhere. Just give JSON or YAML or anything really but XML…

      But to each their own i guess.

    • Gremour@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      2 months ago

      YAML for human-written files, JSON for back-to-front and protobuf for back-to-back. XML is an abomination.

    • Takumidesh@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      2 months ago

      I hate writing and reading xml compared to json, I don’t really care if one is slightly leaner than the other. If your concern is the size or speed you should probably be rethinking how you serialize the data anyway (orotobuff/DB)

  • AeonFelis@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 months ago

    XML is good for markup. The problem is that people too often confuse “markup” and “serialization”.

  • SzethFriendOfNimi@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    2 months ago

    It’s not a waste of time… it’s a waste of space. But it does allow you to “enforce” some schema. Which, very few people use that way and so, as a data store using JSON works better.

    Or… we could go back to old school records where you store structs with certain defined lengths in a file.

    You know what? XML isn’t looking so bad now.

    If you want to break the AI ask instead what regex you should use to parse HTML.

  • Anna@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    2 months ago

    Is this a tactic used by skynet to lure all humans together and then…BANG!!!

  • ZILtoid1991@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    2 months ago

    XML has its strengths as a markdown format. My own formatted text format ETML is based on XML, as I could recycle old HTML conventions (still has stylesheet as an option), and I can store multiple text blocks in an XML file. It’s not something my main choice of human readable format SDL excels at, which itself has its own issues (I’m writing my own extensions/refinements for it by the name XDL, with hexadecimal numbers, ISO dates, etc.).

    • Serinus@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      2 months ago

      Disagree. I prefer XML for config files where the efficiency of disk size doesn’t matter at all. Layers of XML are much easier to read than layers of Json. Json is generally better where efficiency matters.