Hacker News Reader

Comment by meander_water | Hacker News Reader

I don't get it, can't you just use yaml instead of inventing another DSL.

For repeating objects of the same structure, yaml will still require each key on each object, whereas this is a hybrid with csv, so it defines the keys once.

No one forces us to use objects in JSON with repeated keys you know.

Indeed a

    {"header": ["some","column","names"], "values": [[1,2,3],[4,5,6],...]}

could fit.

For sure, but most people aren't thinking intentionally about what they are dumping into their context either ;)

It's more compact than YAML. More like a combination of YAML and CSV.

Norway.

YAML 1.2 has been out for 16 years now, so I would simply not assume that the suggestion to use YAML for a new purpose means “use YAML 1.1”.

I could agree that you would not make poor assumptions.

Your LLM, however, may experience cross-format feature superposition and consequential spurious activation.

It is, also noone uses it:)

This TOON is bound to have the same problem, because strings are not quoted. You can’t differentiate between the number 123 and the string ”123”.

For LLM consumption, this might not matter, don’t use this for anything else.

Reply on news.ycombinator.com