14 ms·
For a pragmatic, really readable configuration file format, TOML never disappointed me ( https://github.com/toml-lang/toml#user-content-local-date https://githu
by adev_ 7y ago
For a pragmatic, really readable configuration file format, TOML never disappointed me ( https://github.com/toml-lang/toml#user-content-local-date https://github.com/toml-lang/toml#user-content-local-date ).
- This is human readable contrary to the JSON family and its {} abuses.
- It is not space / ident base contrary to YAML that becomes very quickly a mess to write and a mess to parse.
- epage 7y agoAs a fan of TOML, I want to be clear on the downsides. TOML is good for data layed out with TOML. Representing arbitrary nested arrays and tables gets messy. Also, the constraint on homogenous shallow types has impacted me in some cases. Originally, I was all on board. Arrays should be homogenous. The problem is logically homogenous vs syntactically homogenous. Cargo uses tables to declare dependencies. The values are logically homogenous, they are declarations. Synatictically, some values are strings while the rest are sub-tables. The string is just shorthand for a table though. This feature can't be implemented in arrays like it can with tables.
- nikolay 7y agoTOML is almost perfect. The only things I don't like are the need for commas and the double brackets.
- smitty1e 7y agoPerfection is a bugaboo. Give me 95%, minor inconveniences, and declare vict'ry, say I.