sexp VS hjson

There's a tool sexp that Jane Street uses internally to slice and dice sexp logs, but, yes, I get that there aren't logging services out there that support sexps. They should, though, as sexps have unique advantages over JSON. They tend to be more human-readable too. Great blog post overall!

HJson https://hjson.github.io seems a nice 'in-between' between YAML and JSON without the indentation-based syntax, so closer to the JSON side but with comments and less quotes.

What I don't really get is why the cloud providers / tooling implementors have never drafted up a "YAML-light" that just throws out the rarely-used headache-inducing syntax elements.

Hjson is very similar to JSON5 but allows quotes to be dropped and can use newlines instead of commas. There are implementations for a lot of different languages, I myself contributed the C++ implementation. I wanted something smaller than Yaml but more lax than JSON, found Hjson to suit my needs perfectly.

https://hjson.github.io/

JSONs make terrible config files. If you want to use json-like syntax for config, use hjson instead. It's basically json, but changes it slightly so it better matches human expectations.

```

YAML and JSON succeeded because they had a clean and predictable, no-nonsense mapping between encoding and object-model after decoding. Probably we should all switch to an almost-yaml format that does away with the peculiarities, and the FANG companies would have the momentum to make that happen.

I personally would like for HJSON (https://hjson.github.io) to see more adoption, but that train has passed...

There’s also json-c and Hjson.