6 ms·

Please no json file, use yaml or have an option for yaml T___T. The curly braces and brackets can get ugly when nested. edit: It may seems stupid but when yo

Please no json file, use yaml or have an option for yaml T___T. The curly braces and brackets can get ugly when nested. edit: It may seems stupid but when you're on the terminal with vim and the directory path is long in some nested object/array. Things is really hard to parse out with your eyes.

ecnahc515 12y ago
I think using JSON is a solid choice. You can easily make yaml to JSON translators for this purpose.
- ash 12y ago
  JSON is okay, but I hope TOML will gain traction soon. Because comments. And trailing commas. Rust Crate is already using TOML for package metadata. https://github.com/toml-lang/toml https://github.com/toml-lang/toml http://doc.crates.io/manifest.html http://doc.crates.io/manifest.html
  - bjt 12y ago
    I've been -1 on TOML for a long time, and preferred YAML, but your point about comments is persuading me.
  - nor0101 12y ago
    +1 for TOML, started playing with Rust a couple of weeks ago.
  - catwell 12y ago
    +1 for TOML. If you think simplicity matters, look at the YAML spec [1], vomit and never use it again. If you still don't believe me, try implementing a conforming YAML 1.2 parser (oh, and try not to make it a source of RCE [2]...). [1] http://yaml.org/spec/1.2/spec.html http://yaml.org/spec/1.2/spec.html [2] http://blog.codeclimate.com/blog/2013/01/10/rails-remote-code-execution-vulnerability-explained/ http://blog.codeclimate.com/blog/2013/01/10/rails-remote-cod...
  - pnathan 12y ago
    +2 on Toml, it's a great config file language.