[rust-dev] Configuration files library for Rust

Michael Neumann mneumann at ntecs.de
Sat Jan 4 12:32:54 PST 2014

Am 04.01.2014 21:30, schrieb Tony Arcieri:
> On Sat, Jan 4, 2014 at 12:26 PM, Gaetan <gaetan at xeberon.net 
> <mailto:gaetan at xeberon.net>> wrote:
>     I m interessed on having your feedback on json and yaml vs toml
>     for instance.
> JSON is ugly and token-ridden for configuration files. Having worked 
> with tools that use it for this purpose, I find the configuration hard 
> to read. Then there's the issue of comments, which are particularly 
> important for configuration files. Some things have adopted JS-style 
> comments for this purpose, but that's technically not standard JSON.
> YAML's problem is indentation errors can turn into configuration 
> errors, and they're incredibly tricky to spot. I've run into cases 
> where we didn't spot problems until we deployed to production because 
> the "production" section of a configuration file was misindented.

And, I think it's pretty hard to write a YAML parser. The spec is pretty 
extensive. Whereas a TOML or INI parser, you can hack within a few hours.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/rust-dev/attachments/20140104/f065104b/attachment.html>

More information about the Rust-dev mailing list