3 ms·
I only opened this article to see a comparison with FlatBuffers and got disappointed. :( To be fair though, I am open to the idea of having a separate schema d
by pdimitar 6y ago
I only opened this article to see a comparison with FlatBuffers and got disappointed. :(
To be fair though, I am open to the idea of having a separate schema definition language, at least. (And please don't say DDL, it doesn't even come close.)
- schoetbi 6y agoAgree, the ecosystem for flatbuffer and the perfomance is great. Here is the language support: https://google.github.io/flatbuffers/flatbuffers_support.html https://google.github.io/flatbuffers/flatbuffers_support.htm...
- otabdeveloper4 6y agoFlatBuffers 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.
- pdimitar 6y agoI don't see why C++ considerations get priority over everything else, or are you making another point?
- otabdeveloper4 6y agoThey do get priority when you're primarily coding in C++, obviously. Not everything is Javascript-first. Different requirements for different folks.
- pdimitar 6y agoI 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?
- otabdeveloper4 6y agoNever used this Bebop thing, but I'd have definitely preferred it to FlatBuffers back when I was shopping for serialization libraries.