"It's a complex problem so we just cast everything to a sting and require applications to handle the typing" is what I interpret it as. Honestly after a few ye

"It's a complex problem so we just cast everything to a sting and require applications to handle the typing" is what I interpret it as. Honestly after a few years using YAML you remember to always quote anything you know you need to be a string, and the different multi line types. An argument against this is "why not just design it to be simpler" — well, then it's less useful in as wide a variety of applications, and stands less chance of actually becoming a standard like JSON or YAML has. And you end up with the XKCD problem. YAML came in and solved a few of JSON's most glaring problems (multi line and comments) with a usable approach. This new format seems like it's "YAML, but a little different." If I wanted to usurp YAML, I'd focus on the greatest pain points for most, whitespace and schema support.