NB here is the #YAML #document from #hell [0] encoded in #JDAML.

I'm designing #JDAML to eliminate the risk of accidental interpretation. Unless a leaf value is clearly explicitly marked in a predictable manner, it will be interpreted as a #string.

So no #norwayproblem, no #sexagesimal or other weird number literals. No #anchors, #aliases, or #tags. No accidental non-string keys, no accidental numbers.

[0] as described by Ruud van Asseldonk in this article: https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell

The yaml document from hell

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.

Today in #NorwayProblem bugs: The `tan()` function triggers the color picker

https://bugs.webkit.org/show_bug.cgi?id=265254

As webKit developers say:

"Well, this is embarrassing :)"

265254 – Web Inspector: The `tan()` function triggers the color picker

@arestless I was burned once by #YAML: https://hitchdev.com/strictyaml/why/implicit-typing-removed/

My unix username is the single character `n`. This evaluated to false, and I kept encountering bugs that my colleagues didn't... #norwayproblem

The Norway Problem - why StrictYAML refuses to do implicit typing and so should you - HitchDev