|
|
|
|
|
by rdtsc
3612 days ago
|
|
How does this compare or in general why would you pick this vs newer formats like Cap'n'proto or FlatBuffers? From FlatBuffers overview I see this comparison: --- Protocol Buffers is indeed relatively similar to FlatBuffers, with the primary difference being that FlatBuffers does not need a parsing/ unpacking step to a secondary representation before you can access data, often coupled with per-object memory allocation. The code is an order of magnitude bigger, too. Protocol Buffers has neither optional text import/export nor schema language features like unions. --- So are the newer ones useful mostly when serialization vs deserialization speed matters (https://google.github.io/flatbuffers/) ? |
|