5 ms·

I think that's a good point. Why use .toml when we have better alternatives already? (I admit I have a bias against toml, but still...)

• the_mitsuhiko 12y ago
  Which ones would that be?
  • mateuszf 12y ago
    How about s-expressions :) ?
    • bjz_ 12y ago
      That would be my choice, but TOML is good enough for me :)
    • bokchoi 12y ago
      Or edn? https://github.com/edn-format/edn https://github.com/edn-format/edn
  • phloxicon 12y ago
    YAML is quite mature, clean, is a superset of JSON so people could use JSON if they wanted, and it's used for config files for pub, Dart's package manager. TOML doesn't seem mature enough.
    • bjz_ 12y ago
      TOML is extremely simple. YAML on the other hand is incredibly hard to implement. JSON has no comments and is not really that nice for humans.
  • nimish 12y ago
    toml is unstable and has no real spec + YAML has a well defined spec and is widely used?
    • Ygg2 12y ago
      YAML spec is also super complicated and writing parser for it is non-trivial (for comparisson YAML has ~150 EBNF rules while XML with DTD has about ~80)! I'm not comparing validation rules but they are probably about the same. This complexity means there is already a parser for TOML, and not one for YAML. That's IMO main reason they went with TOML.
      • steveklabnik 12y ago
        There are actually already MULTIPLE parsers for TOML in Rust, and Cargo switched between the two yesterday. As you say, this is a testament to TOML's simplicity. EDIT: Furthermore, TOML is going to have a 1.0 soon: https://github.com/rust-lang/cargo/issues/46 https://github.com/rust-lang/cargo/issues/46
  • kodablah 12y ago
    HOCON: https://github.com/typesafehub/config https://github.com/typesafehub/config