> On 9 Oct 2019, at 14:49, PBKResearch <pe...@pbkresearch.co.uk> wrote:
>
> Sven
>
> Excellent. Can the same idea be extended to STON - or is it there already?
I did not (yet) consider that, I will think about it.
However, Pharo contains two serialisation formats out of the box, STON, which
is a textual format focusing on domain model objects, and FUEL, which is a fast
binary format that can serialise special system objects as well.
> Peter Kenny
>
> -----Original Message-----
> From: Pharo-users <pharo-users-boun...@lists.pharo.org> On Behalf Of Sven
> Van Caekenberghe
> Sent: 09 October 2019 13:29
> To: Any question about pharo is welcome <pharo-users@lists.pharo.org>
> Subject: [Pharo-users] [ ANN ] Neo Universal Binary JSON
>
> Hi,
>
> I just published an implementation of Universal Binary JSON (UBJSON) for
> Pharo.
>
> https://github.com/svenvc/NeoUniversalBinaryJSON
>
> Universal Binary JSON (UBJSON) is a computer data interchange format. It is
> a binary form directly imitating JSON, but requiring fewer bytes of data. It
> aims to achieve the generality of JSON, combined with being easier and more
> efficient to process than JSON.
>
> http://ubjson.org
> https://en.wikipedia.org/wiki/UBJSON
>
> The size/speed/efficiency differences are minor for typical JSON payloads,
> especially compared with compacted JSON. The implementation is simpler,
> though, as there is no string escaping and no number parsing.
>
> UBJSON is making a larger difference when dealing with arrays containing
> numbers. Especially with ByteArrays, UBJSON makes a huge difference, since
> these are essentially stored natively.
>
> Sven
>
>
>
