Skip Navigation

You're viewing a single thread.

58 comments
  • For serializing? I'd probably just go with json.

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

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

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

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

58 comments