Hacker News Reader

Parent Full thread

coldtea

The author is right, both JSON and XML are better for configuration files.

Non ambiguous structure, parsable, nested values, lists, maps, and so on.

If JSON had comments it would be ideal - and for configuration you can support it.

Just check VS Code for what is possible to do directly regarding configuration with JSON, and also to build on top.

View on HN

YAML is a superset of JSON, so if you prefer JSON, you can - any valid JSON is also valid YAML.

Depending on the yaml parser's quirks.

It is, but then you just use JSON, and can ignore YAMLs design issues and broken design, plus benefit from the mass more readily available and faster parsers!

json5 for complex config files is quite nice.

Reply on news.ycombinator.com