• schnurrito@discuss.tchncs.de
    314·
    10 days ago

    IMHO: XML is a file format, JSON is a data transfer format. Reinventing things like RSS or SVG to use JSON wouldn’t be helpful, but using XML to communicate between your app’s frontend and backend wouldn’t be either.

      • MonkderVierte@lemmy.ml
        62·
        10 days ago

        The amount of config.jsons I’ve had to mess with…

        Yeah, json is not a good config format. As much as xml is not. Please use something like YAML or TOML.

        • sysop@lemmy.world
          7·
          9 days ago

          I never moved away from ini I’ve just been sititng back watching you all re-invent the wheel over and over and over and over and over.

          • reinei@lemmy.world
            2·
            9 days ago

            It’s a wheel, it’s supposed to turn over and over and over ad infinitum!

            /S (because it’s big sarcasm instead of small.)

        • toastal@lemmy.mlEnglish
          1·
          9 days ago

          I wish more things used Nickel or Dhall for config. I don’t know why I wouldn’t want editor support for type information or the ability to make functions in my non-Turing-complete config to eliminate boilerplate on my end.

      • schnurrito@discuss.tchncs.de
        21·
        10 days ago

        Of course you can use XML that way, but it is unnecessarily verbose and complex because you have to make decisions, like, whether to store things as attributes or as nested elements.

        I stand by my statement that if you’re saving things to a file you should probably use XML, if you’re transferring data over a network you should probably use JSON.