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

      • Lysergid@lemmy.ml
        5·
        3 months ago

        Yaml is dogshit format. If you need tree-like structure use json if you need list of props use toml or simple key value pairs. I fucking hate app properties in yaml.

        • can’t search shit
        • copy-paste doesn’t “just work” when you want to merge two files
        • your editor doesn’t show whitespaces and you messed up somewhere - valid but incorrect
        • messed up formatting your list of banned IPs/hosts/ports/users/subnets/commands - get pwned

        It should’ve never left the basement of crackhead who thought “let’s make schema-less format depend on number of invisible characters”.

        I’ll rather save my data in Copybook and record it on tape then use this Python-bastardized abomination

        • abbadon420@sh.itjust.works
          2·
          3 months ago

          Oh nice! I didn’tknow toml, so I looked it up a bit. Atfirst I was like “this is just .properties with a better typing support”. Than I saw the tables and the inline tables, which is a really neat way for complex nesting. It reminds me of json, but better. I’ll see if I can start using this somewhere.

        • Tanoh@lemmy.world
          5·
          3 months ago

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

            • abbadon420@sh.itjust.works
              6·
              3 months 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.

            • bleistift2@sopuli.xyzEnglish
              2·
              3 months 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).

            • tyler
              23·
              3 months ago

              Now do a second comment.

                • tyler
                  1·
                  3 months 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.

    • neukenindekeuken@sh.itjust.works
      12·
      3 months ago

      Json configs read much cleaner to me since .net swapped to them a while back.

      Xml is incredibly verbose when there’s a 12k loc web.config.xml

      • MonkderVierte@lemmy.zip
        2·
        3 months ago

        Then do a cfg or ini style config or make multiple config files. YAML/TOML if you can’t make it simpler. The neccessity for complex config formats is a fuckup of the dev.