YAML for configuration files?
Closed this issue · 4 comments
JSON files are hard for typical users. YAML?
d0f7fb4 completes this. Changes configuration completely.
:| -- I understand that JSON is awful for users to build. I've just always hated YAML. I guess that just gives me encouragement to build some UI for configuration so I don't need to look at raw YAML ever 😃
I'm not a fan of YAML either, mostly because of the disparity between implementations. At least JSON works reliably and the old json-tidy implementation fixed up any errors users might've introduced.
The problem is
- ini files can't support the current complexity
- xml is nasty
- (valid) json is confusing to non-programmers
- old style tidied json is still confusing to non-programmers
- yaml has spacing issues but most users get
- writing a configuration file parser is dull :(
I'm open to alternatives though :) I'm half tempted to allow for yaml and json-tidy, it would be trivial to add back.
I just like JSON, then again I understand JS sometimes :p. XML ironically is probably what people would get the most, but it's ugly and awful.
Regardless, having a simple UI regardless of format could be useful (starting it with xi4n -w or whatever) could start a simple Express server with a simple UI to add/remove plugins. That is totally for polish of the whole system though, and probably not for this stage of development. Would be useful, however plugins would require the ability to return a "config" object.