News for hackers. Stuff that matters.
Re:Hjson, the Human JSON by alanh on Thursday April 14, 2016 @05:07PM (#11500354)
YAML is more complex that most people tend to realize. (This was brought up in a 2011 discussion about possibly standardizing a metadata section for Markdown documents which sadly went nowhere. [1])

Take a look at example 2.11 in the YAML spec [2], for example, and see if you can make heads or tails of it.

[1]: https://pairlist6.pair.net/pipermail/markdown-discuss/2011-A...

[2]: http://www.yaml.org/spec/1.2/spec.html#id2760395

Re:Hjson, the Human JSON by detaro on Thursday April 14, 2016 @06:08PM (#11500718)
pyYAML has this collection of problems with the spec: http://pyyaml.org/wiki/BugsInTheYAMLSpecification

(and pyYAML itself can't always parse its own output correctly...)

Re:Hjson, the Human JSON by crdoconnor on Thursday April 14, 2016 @05:56PM (#11500639)
You don't need most of those features. A pared down YAML with the cruft removed (implicit typing, flow style, tag tokens, node anchor & references) is actually pretty simple as well as less "gotcha-y".
Re:Hjson, the Human JSON by __david__ on Friday April 15, 2016 @03:57AM (#11502853)
Sure, but most language YAML parsers support all or most of the spec. That can be a problem if you aren't expecting it.
Re:Hjson, the Human JSON by alanh on Friday April 15, 2016 @07:11PM (#11508311)
I believe it has even created security issues. Didn’t Rails have at least one YAML-based vuln?
Re:Hjson, the Human JSON by rurban on Sunday April 17, 2016 @12:19PM (#11515039)
You need to restrict YAML to SecureLoad, with manually adding allowed typed and classes.

At least perl doesn't support this, so it's inherently insecure there, but you can always use YAML::Syck which didn't go this way.