skepllerFeb 24

TOML

https://lemmy.world/post/43529621

Show threadqevlarrFeb 24

Time to read this if you haven’t already

ruudvanasseldonk.com/…/the-yaml-document-from-hel…

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.

Show threadLiveLMFeb 24

The json spec is not versioned. There were two changes to it in 2005 (the removal of comments

See, this is why we can’t have nice things.

Show threadEpheraFeb 25
I can kind of understand it after having to work with an XML file where users encoded data into comments for no good reason. But yeah, it does make JSON awkward for lots of potential use-cases.
Show threadMonkderVierteFeb 25
Hm? Comments are not data.
Show threadtetris11Feb 25
They are useful metadata important to the longterm lifespan of the codebase
Show threadflying_sheep
That’s why they make sense in code and config files. JSON is neither, despite the insistence of far too many people to write configuration in it.
Feb 25 at 2:29pmWeb
Show threadtetris11Feb 25
In an ideal world, yes. In a locked down world where you have access only to 1/4 the codebase or your job is more ontology-focused, all you have access to might be the JSON. Leaving a comment or two about why a particular value or hierarchy is as it is is sometimes more clear than writing up a seperate README that no one will read