-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Closed
Description
You mention memory efficiency as the main selling point of flatbuffers. However, capnp already exists, with zero copy "serialization," and a range of compelling features (RPC, etc). Still you saw the need to build flatbuffers, which means this library either (a) does something capnp doesn't, or (b) beats capnp in some respect. Could you please describe somewhere what this rationale is? Why should someone pick flatbuffers instead of capnp?
timotheecour, KishoreVignesh, ostrokach, zautomata, bugproof and 26 more
Metadata
Metadata
Assignees
Labels
No labels