• abhibeckert@lemmy.world
    link
    fedilink
    English
    arrow-up
    15
    arrow-down
    1
    ·
    edit-2
    1 year ago

    Uh no, the worst is a tie between XML and JSON.

    XML because the syntax is hard to read and even harder to write, and JSON because you can’t do comments. WTF.

    • atzanteol@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      6
      arrow-down
      2
      ·
      1 year ago

      XML is a bit verbose but otherwise easy to understand. JSON5 supports comments.

      And neither requires me to explain weird formatting nuances to devops engineers.

      YAML is a pain to read (lists of structures are very messy), can’t be auto-formatted, and is full of weird “gotchas” (Norway, errant tabs, etc.) if you don’t do things “the right way.”

      Requiring the use of whitespace in formatting is wrong. End of.

        • atzanteol@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          5
          ·
          1 year ago

          Oh, yeah, nothing like telling a dba they’re using the wrong editor when they’re trying to configure something.

          If your config format requires specific editors you’re using the wrong format.

    • jmanjones@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      1 year ago

      I instant exit on XML conf files. I have no idea how to parse the info, maybe I should. But there are too many tags and my eyes instantly glaze over when I see it!