2 ms·
I'm building a new twin ad-hoc encoding format to replace JSON and friends [1]. It has native support for all commonly used data types, so you don't need to ar
by kstenerud 7y ago
I'm building a new twin ad-hoc encoding format to replace JSON and friends [1].
It has native support for all commonly used data types, so you don't need to artificially specify custom encodings just to get your data across.
It's a twin text / binary format, where the text format can be transparently converted to the binary format, and vice versa. This means that you can use the binary format for storage and communication, and only convert to/from the text format when humans get involved.
I'm currently building a reference implementation in go [2], which is now running faster than the JSON codec in my experimental branch [3].
[1] https://github.com/kstenerud/concise-encoding#concise-encoding https://github.com/kstenerud/concise-encoding#concise-encodi...
[2] https://github.com/kstenerud/go-cbe https://github.com/kstenerud/go-cbe
[3] https://github.com/kstenerud/go-cbe/tree/new-implementation https://github.com/kstenerud/go-cbe/tree/new-implementation
- lukevp 7y agoBenefits vs capn proto or grpc?
- kstenerud 7y agoThere's a basic comparison here: https://github.com/kstenerud/concise-encoding#comparison-to-other-formats https://github.com/kstenerud/concise-encoding#comparison-to-...
- BatFastard 7y agoThat looks amazing! Best of luck.