3 ms·

My favorite so far is StrictYaml [1]. It's a subset of yaml that directly addresses a lot of the article's concerns: * supports comments * flexible with good

My favorite so far is StrictYaml [1]. It's a subset of yaml that directly addresses a lot of the article's concerns: * supports comments * flexible with good signal to noise (no need for so many brackets and commas) * gets rid of a lot of YAML's complexity [2] * explicitly typed for less ambiguities [3] The main page also gives comparisons against HJSON, HOCON and TOML [4] [1]: https://hitchdev.com/strictyaml/ https://hitchdev.com/strictyaml/ [2]: https://hitchdev.com/strictyaml/features-removed/ https://hitchdev.com/strictyaml/features-removed/ [3]: https://hitchdev.com/strictyaml/why/implicit-typing-removed/ https://hitchdev.com/strictyaml/why/implicit-typing-removed/ [4]: https://hitchdev.com/strictyaml/#why-strictyaml https://hitchdev.com/strictyaml/#why-strictyaml

Spivak 4y ago
StrictYAML throws out too much for my taste — tags, flow state, and anchors are all useful non-footgun features.
- woojoo666 4y ago
  To me those are in the category of "nice to have", and the problem is that every developer has different preferences for these [1] [2]. But the main features of StrictYaml, like supporting comments and less syntactic noise, I think are pretty uncontroversial, and perhaps it's worth it to get people to switch over for those alone. It doesn't need to be perfect, it just needs to be a significant enough improvement over JSON, and I'd say those two features are more than enough [1]: https://github.com/crdoconnor/strictyaml/issues/37 https://github.com/crdoconnor/strictyaml/issues/37 [2]: https://github.com/crdoconnor/strictyaml/issues/38 https://github.com/crdoconnor/strictyaml/issues/38