News for hackers. Stuff that matters.
Re:Better Than JSON by jonny_eh on Monday December 01, 2025 @07:24PM (#46115595)
Is that a format/serialization issue, or library/implementation issue?
Re:Better Than JSON by __s on Monday December 01, 2025 @10:09PM (#46116982)
Re:Better Than JSON by ElectricalUnion on Monday December 01, 2025 @10:14PM (#46117030)
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.

Re:Better Than JSON by TillE on Monday December 01, 2025 @11:40PM (#46117616)
Google has a library/format for that too, with FlatBuffers. Different use cases and advantages really, not clearly better/worse.
Re:Better Than JSON by kragen on Tuesday December 02, 2025 @05:43AM (#46119835)
Kenton Varda also worked on Protobufs at Google before he wrote CapnProto, I think.