Hacker News Reader

Comment by freedomben | Hacker News Reader

You can find absurd behavior during corner cases in nearly any non-trivial language. YAML is a great language when you need to represent objects in something universal and human readable/writable. Not perfect of course, but TOML's limitations can turn stuff into a monstrosity with it's limitations. Ansible inventory files come to mind here.

View on HN

One can find absurd behavior in corner cases of any non-trivial language, but one can find absurd behavior in YAML without even looking for it.

Such as? All these cases with no and norwegian or whatever but I haven't run into major problems and use it frequently.

e: And, AFAIK, I believe the latest YAML 1.2 spec (from 2009) has addressed these issues.

I use it frequently too, but there's some terrible edge cases: https://stackoverflow.com/questions/53648244/specifying-the-...

? I don't think these are issues with Yaml 1.2, the spec since 2009.

What about `thing: 1.0` and `thing: 1.0.0`?

Parser implementations have also been buggy. The ruby one in particular being a source of RCE's. Of course, these are implementation issues, but surely a simpler specofication would be easier to implement. And the current specification is anything but simple, clocking 84 pages in the PDF flavour.

The "no"/"norwegian" thing is emblematic of very sloppy thinking in YAML's design, and it's far from the only example.

It's possible to avoid these pitfalls - like people do with PHP - but why burden users with that in a new project when better options have been available for years?

They obviously like Rust, why not just follow their lead with TOML?

That "feature" regarding "no" hasn't even been present in the YAML spec since 2009.

Thanks for being clear about this and repeating it. I didn’t know. I think I will only use YAML 1.2 as configuration language.

The NO alone should give you pause...

It's a language that coerces basic strings...

Reply on news.ycombinator.com