And I’ll show you YAML

(a continuation of this post)

  • synae[he/him]
    link
    fedilink
    English
    251 year ago

    For serializing? I’d probably just go with json.

    For content meant to be written or edited by humans? YAML all day baby

    • @[email protected]
      link
      fedilink
      51 year ago

      Ever tried NestedText? It’s like basic YAML but everything is a string (types are up to the code that ingests it), and you never ever need to escape a character.

      • synae[he/him]
        link
        fedilink
        English
        91 year ago

        I’ve got too many consumers that I don’t control which dictate their input formats. And to be quite honest, “types are up to the code that ingests it” sounds like a huge negative to me.

        • @[email protected]
          link
          fedilink
          31 year ago

          Ah, well I love that policy (types being in code, not configs). FWIW I sometimes use it as a hand-edited document, with a small type-specifying file, to generate json/yaml/toml for other programs to load.