FlatBuffers creates its own demented and completely incompatible data structures when deserializing into C++. Which means you then need to copy the FlatBuffers structures into normal ones, defeating the entire point of "zero-copy" in the first place.

This thing it looks like uses normal C++ structures under the hood, and if so that's a huge plus.

I don't see why C++ considerations get priority over everything else, or are you making another point?

They do get priority when you're primarily coding in C++, obviously. Not everything is Javascript-first. Different requirements for different folks.

I am not a JS dev, don't project your frustration on me. ;)

So okay, FlatBuffers doesn't map its zero-copy philosophy perfectly everywhere -- fact of life. What would you offer then? Which other format and/or library?

Never used this Bebop thing, but I'd have definitely preferred it to FlatBuffers back when I was shopping for serialization libraries.

Agree, the ecosystem for flatbuffer and the perfomance is great. Here is the language support: https://google.github.io/flatbuffers/flatbuffers_support.htm...