Hacker News Reader

> I have no idea how to help with YAML omnipresence in Kubernetes. More than a half of my problems at a $daily_job

There are two good features in YAML: multiline strings, and YAML is a JSON superset. You can use anything that generates JSON to generate YAML.

Nickel can be evaluated to JSON: https://nickel-lang.org/

View on HN

> YAML is a JSON superset

On the sense that any JSON file is a valid YAML file.

But absolutely not in the sense that you can just treat your json file as YAML and expect it to contain the correct data.

Hm, what JSON documents have a different meaning in YAML? I'd have hoped that with all names & strings being quoted and leading zeros being disallowed, that wouldn't be the case.

I have never come across a case where JSON can't take the place of YAML, but I guess there could be edge cases.

You can easily corrupt the meaning of your JSON by adding whitespace in YAML.

Maybe duplicate keys in JSON counts? Some JSON parsers choose the first and some choose the last, and YAML directly forbid that.

Exactly my thought.

Is it that an academic property, or are people serious about throwing JSON into running software that parses YAML and expect good results? (Should I add: on production, because I want my tools to be used on production, but that's just me)

Reply on news.ycombinator.com