As a data format, yaml is extremely complicated and it has many footguns. In this post I explain some of those pitfalls by means of an example, and I suggest a few simpler and safer yaml alternatives.
A 10 minute read covering some YAML edge-cases that you should have in mind when writing complex YAML files
If you’re comparing YAML with JSON, it displays that you understand neither.
JSON is designed for data exchange between systems. YAML is designed to describe data for a single system, and is always subject to individual implementations.
They are both serialization formats that are supposed to be able to represent the same thing. Converting between these 2 formats is used in the article as a way to highlight yaml’s parsing quirks (since JSON only has a single way to represent the false boolean value, it makes it clear that the no value in yaml is interpreted as a boolean false and not as the "no" string)
Anyway, I disagree with your point about YAML and JSON not being interchangeable
If you’re comparing YAML with JSON, it displays that you understand neither.
JSON is designed for data exchange between systems. YAML is designed to describe data for a single system, and is always subject to individual implementations.
They are not interchangeable concepts.
all json is valid yaml and can be parsed with a yaml parser. Yaml is literally a superset of json. In what world are they not comparable?
YAML 1.2 is a superset of JSON. Every valid JSON is valid YAML 1.2
They are both serialization formats that are supposed to be able to represent the same thing. Converting between these 2 formats is used in the article as a way to highlight yaml’s parsing quirks (since JSON only has a single way to represent the
falseboolean value, it makes it clear that thenovalue in yaml is interpreted as a booleanfalseand not as the"no"string)Anyway, I disagree with your point about YAML and JSON not being interchangeable