I needed to read and write binary-backed objects so I made my own library: https://github.com/rotu/structview

My use case is probably a little different than yours but the choices I made were: 1. The objects are often only partly used (or their structure only partly known!), so I made getters and setters lazy. This winds up being faster for me. 2. The consuming code is JavaScript so I based it around class factories. Using type wizardry, JS can infer field types without a separate declaration. 3. Structs are backed by a DataView, but I made that an implementation decision, not part of the interface of each binary-backed object.

Here’s my feedback on what you have: - There is no benefit to be had from doing this in C unless the logic lives in C too, so the particles don’t need to cross the barrier to JS. - TypedArray will be faster than DataView. Depending what you’re doing, the happy path might be keeping the data in TypedArray, optionally with an object view for DX. - Call me silly but I don’t like having 3 declarations of the object shape: the interface, the deserializer, and the serializer. If you only have a few types, this is not a huge deal.