• ryathal@sh.itjust.works
      312·
      1 day ago

      XML is ok for complex docs where you have a detailed structure and relationships. JSON is good for simple objects. YAML is good for being something to switch to for the illusion of progress.

      • Radioactive Butthole@reddthat.comEnglish
        8·
        1 day ago

        Meh. I just wish XML was easier to parse. I have to shuttle a lot of XML data back and forth. As far as I can tell, the only way to query the data is to download a whole engine to run a special query language, and that doesn’t really integrate into any of my workflows. JSON retains the hierarchy and is trivially parsed in almost any programming language. I bet a JSON file containing the exact same data would be much smaller also, since you don’t list each tag twice.

          • Radioactive Butthole@reddthat.comEnglish
            1·
            6 hours ago

            That’s kind of my point though. For being made specifically for the purpose of being machine readable, its kind of a pain in the ass to work with.

            I want a command line utility where I can just

            xmlquery --query 'some/query' --file foo.xml --output foo-out.xml

            or in python

            
import xml

with open("foo.xml", "r") as file:
    data = xml.load(file.read())

            That’s the amount of effort I want to put into parsing a data storage format.

    • jonne@infosec.pub
      7·
      1 day ago

      It’s still using the lesser of 3 evils, we need a fourth human readable data interchange format.