CBOR for the binary format? #8
Description
The README currently says "Binary Format \ Note: this part is still vaporware \ An optimized binary representation that omits field names and avoids escaping strings." I suggest that designing a binary format from scratch may be some work and, while there are good reasons for creating a new text format like Ziggy, creating a new binary format may be too much. Why not using CBOR, standardized in RFC 8949?
- It already exists, with a lot of implementations,
- It is optimized for storage space, and simplicity of parsers,
- Its data model is very close from the one of JSON so it seems it would be fine for Ziggy.