Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Is that a format/serialization issue, or library/implementation issue?




Serialization issue. From the Introduction to Cap’n Proto:

"Cap’n Proto is INFINITY TIMES faster than Protocol Buffers. (...) there is no encoding/decoding step. The Cap’n Proto encoding is appropriate both as a data interchange format and an in-memory representation, so once your structure is built, you can simply write the bytes straight out".

I take it as a rationalization of what OLE Compound File Binary - internal Microsoft Office memory structures serialized "raw" as file format - would look like if they paid more attention to being backward and forward compatible and extensible.


Google has a library/format for that too, with FlatBuffers. Different use cases and advantages really, not clearly better/worse.

Kenton Varda also worked on Protobufs at Google before he wrote CapnProto, I think.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: