Re:Textual configuration has comments, GUIs don't.
by FooBarWidget on Thursday June 30, 2011 @11:23AM
(#2714394)
JSON is meant to be a serialization language, not a config file language. Therefore it strips out all the things that it doesn't need. If you want a config file language then use YAML which is a much better candidate.
Re:Textual configuration has comments, GUIs don't.
by amalcon on Thursday June 30, 2011 @11:37AM
(#2714446)
Yes, YAML is very nice. Importantly, it reduces to key:value for the 90% of config files that don't require any hierarchy while still allowing hierarchy if you need it.
I'm not sure I buy the serialization argument, though: it's a human-readable serialization format. One of the big advantages of human-readable formats is that you can craft data objects by hand (for automated tests, initial bootstrapping, etc). Comments are very helpful for those situations.
Re:Textual configuration has comments, GUIs don't.
by JonnieCache on Thursday June 30, 2011 @01:08PM
(#2714835)
It also has inheritance-like features that make it really suited to config files. JSON really isn't a good idea for config files when we have YAML.
What possible reason could there be for that?