Hacker News Reader

Comment by vkaku | Hacker News Reader

This is great. Good to see standardized testing improvements to the pg_regress add-on. YAML does better than JSON when it comes to readability. To an extent, TOML as well.

View on HN

I couldn't disagree more about YAML. Semantic whitespace is unreadable, as are all the optional language elements. I've been using YAML for years and still can't read it quickly. I find myself asking, "Wait is that a string or boolean? Is it an object or siblings in an array?"

JSON is unambiguous and whitespace agnostic. There's only one way to do things. It's far more readable.

Try adding anything with quotes and multiple lines, and you'll quickly realize that YAML works better than JSON here.

JSON as-is has fewer types and some things are better realized with the JSONNET way than stock.

If I need quotes and multiple lines in a JSON file, it's probably something that shouldn't be a config file.

Either way, JSON5 has been around for years and is a logical update because it brings parity with ECMAScript.

https://mit.cs.uchicago.edu/haohsiang/topics-auction/tree/02....

UCL: https://github.com/vstakhov/libucl

YAML files can be written in JSON format because it is a superset of JSON, which sounds as insane as it is.

It's readable, it just desperately needs type safety: https://github.com/crdoconnor/strictyaml

When I read "gbq enabled: yes" I don't worry about whether it's a string or a boolean when reading it, I worry about whether it's a string or a boolean when I want to change it and it gets parsed again.

Reply on news.ycombinator.com