> On 23 Jun 2023, at 00:06, stephane ducasse <stephane.duca...@inria.fr> wrote:
>
> Super nice
> for a moment I thought that you forgot the final G of the name :)
Haha, that would have been nice.
It is a bit of a weird acronym. I must admit that I did not hear about it until
recently. There are several binary JSON specifications, but this one has an
elegance to it, I liked it immediately. And the best way to understand it or
get a feel for it is to implement it. From time to time I need to do a project
like this: small scope, clear spec, no drama.
I would also like to iterate that doing binary coding in Pharo is really nice,
elegant and powerful.
>> On 21 Jun 2023, at 11:25, Sven Van Caekenberghe <s...@stfx.eu> wrote:
>>
>> [ANN] CBOR for Pharo
>>
>> https://github.com/svenvc/CBOR
>>
>> Concise Binary Object Representation (CBOR) is a binary data serialization
>> format. CBOR is based on the JSON data model: a number of primitive types
>> (integers, floats, booleans, strings and null), lists and maps (which
>> represent objects or structures). Being binary, CBOR is more efficient than
>> JSON, which is text based. CBOR also supports binary data and optional
>> extensions (called tags). This implementation has native support for string
>> and epoch based timestamps (DateAndTime) and big integers (Integer).
>>
>> This project contains encoding/decoding support for the half-precision, IEEE
>> 754 16-bit (binary16) floating-point format.
>>
>> Sven
>>
>>
>> --
>> Sven Van Caekenberghe
>> Proudly supporting Pharo
>> http://pharo.org
>> http://association.pharo.org
>> http://consortium.pharo.org
>>
>>
>>
