What is wrong with TOML? (2019)
The first and the last ones, at least, are tradeoffs where TOML made the right decision for most users.<p>Not being DRY is a good thing in a config file - it makes it much easier to understand and work with just one section of the file (which is what you most often want to do), because the context information is right there without having to jump around and figure things out.<p>And whatever the downsides of syntactic typing are, requiring a schema file to go along with your config file is far more of a downside; it&#x27;s one more point of potential failure, another thing to maintain and sync up and keep in your head, and not worth it for most use cases.<p>And that&#x27;s the crux of it: it all depends on what you need from your markup language, what your use case is, today and through the lifetime of your project. &quot;What&#x27;s wrong with TOML&quot; makes much less sense as a question than &quot;What&#x27;s wrong with TOML(&#x2F;JSON&#x2F;YAML&#x2F;etc.) for _this project and its needs_&quot;.