I have read this critique, and I think it is a good idea to review it before you adopt TOML. That said, I went with TOML for a group of projects recently. My li

I have read this critique, and I think it is a good idea to review it before you adopt TOML. That said, I went with TOML for a group of projects recently. My list projects on GitHub had become difficult to manage as plain Markdown. (They had too many items. The sections were easy to forget to sort. Items in multiple sections had to be kept in sync manually.) I decided to generate the Markdown from a template and serialized data. I evaluated YAML and TOML for storing the data and ended up choosing TOML. What I prefer about TOML for the data I have (dictionaries of dictionaries, no deep nesting) is that the textual representation is flat. I find it easier to read and edit. For comparison, here is one project's TOML data (formatted using https://github.com/tamasfe/taplo https://github.com/tamasfe/taplo with added comments): https://raw.githubusercontent.com/dbohdan/structured-text-tools/ce11203a432bf71bca35bc090e558844500fd7cf/data/projects.toml https://raw.githubusercontent.com/dbohdan/structured-text-to.... Here is the same data converted to YAML with unlimited line width and formatted using https://github.com/google/yamlfmt https://github.com/google/yamlfmt: https://paste.dbohdan.com/projects.1694621084.yaml.txt https://paste.dbohdan.com/projects.1694621084.yaml.txt.