Hacker News Reader

That kind of stops working when (for example) your "payload" is configuration in a file where comments may make sense, though.

I'm more partial to YAML for readability, but I don't think JSON configs are an awful anti pattern.

The exact issue is that JSON's usage spread far beyond "payload."

> It's not code.

package.json has a field literally called 'scripts' where the values are shell one-liners.

This is true, but it is also true that if someone who didn’t read the documentation or the latest version of it, changes a config parameter that brings down a critical system you are responsible for, your bosses or customers won’t care if it was in the documentation or not.

When you are commenting your schema, that's true. Anything which is generated by machines doesn't need comments either. But when it's written by people? And the values? That belongs with the 'payload'.

What about json schema files? Hmmm

Confused puppy look

https://orgmode.org/worg/org-contrib/babel/