@joesabin I’m kind of fine with code bloat, in the sense that we can build software that does a lot more. But json parsing is just… complex, feature-poor and json is an infuriating format and not even that readable to boot.
@mnl Do you have an alternative format in mind?

@andrej

Depending on the use case:
- XML
- protobuf/flatbuf/any decent binary serialization (much easier to handle)

For readability and human consumption: YAML

@mnl Do you have a favorite JSON-datamodel-like binary serialization out of JSONB, BSON, BJSON, UBJSON, CBOR, MessagePack, etc?

Asking partly because it's hilarious that we as a community haven't decided, in fact we're so undecided that at least two of these have IETF RFCs, and partly because you might actually have a preference and offer some insight. πŸ˜ƒ

@andrej

#cerealization

@clacke @andrej I roll with straight json over http for most of my day job web work because the tools and libraries are the easiest to use. For personal use I just use yaml and protobuf.