Comment on Everything about TOML format - Orchard Dweller

• gornius@lemmy.world ⁨9⁩ ⁨months⁩ ago

  What?

  It’s simple and readable. You literally put somebody that has never coded in their life, show them the YAML file and they will probably get it.

  In Toml there are too many ways to do the same thing, which I don’t like. Also unless you know it deeply, you have no idea how the underlying data structure is going to look.

  source

  • eager_eagle@lemmy.world ⁨9⁩ ⁨months⁩ ago

    In Toml there are too many ways to do the same thing, which I don’t like

    ha

    63 different ways to write multi-line strings in YAML

    source

    • BarrierWithAshes@kbin.social ⁨9⁩ ⁨months⁩ ago

      Wow. I've never used yaml or even looked at it but damn that is horrid. Why do people even use this? JSON and XML are so better.

      source

      • NovaPrime@lemmy.ml ⁨9⁩ ⁨months⁩ ago

        I say this with all due respect, but XML can gargle nuts.

        source
      • snowe@programming.dev ⁨9⁩ ⁨months⁩ ago

        Because no one ever uses those. Literally > and | are the only ones I’ve ever seen in over a decade and you will never need to worry about the differences between the two.

        XML as a configuration language is terrible. Yaml gets the point across in an easily readable way, which is exactly the point. Same for JSON except JSON you can’t even use comments (you need json5 or one of the numerous other alternatives to get those).

        source
      • eager_eagle@lemmy.world ⁨9⁩ ⁨months⁩ ago

        It’s really unfortunate the devops world chose such a hot mess of a format. JSONC would be a dumb choice and still do a better job for most config files.

        source
• matcha_addict@lemy.lol ⁨9⁩ ⁨months⁩ ago

  Yaml is already pretty popular, so I don’t think 927 applies here. It’s actually more common in newer projects than toml.

  Which begs the question, should I go with the flow or is there good reason to go with toml?

  source