Bebop v3: a fast, modern replacement for Protocol Buffers
Are protocol buffers not considered "modern" or "fast" anymore? How time flies...
Does Bebop support use as a file format by dumping directly to disk, as some serialization libraries do? Or perhaps a better way to phrase it, since ultimately you can send whatever you want to a binary file, is it intended to be used in such a way?
Never understand the hype for protocol buffers, it may works well for languages like java and kotlin, but is a mess on many other languages. And then there are faster and better replacements.
And all the time I use JSON, there don't exists multiple versions and any JSON file that is somewhere can get read by almost every language. (And I can read the file even with every editor)
I’ve been hoping to see someone eventually build a protobuf style serialisation solution on some of the emerging IETF standards like CBOR and it’s corresponding data definition language.
I’m not really in the market for another proprietary binary data format that doesn’t integrate with anything outside its immediate ecosystem.
Looks great! Is there any chance that Tempo RPC supports TS web clients talking to C# backends? That's our dream.
Update: Coming soon!
Interesting. How does it compare to Slice?
What kind of compatibility guarantees does this make? That's one of the key benefits of protos: I can update clients to add new fields and they can still talk to servers with previous versions of the schema.
This is awesome. I'd love to have upstream support in Wasmer ( https://wasmer.io )
also check out https://github.com/webrpc/webrpc
Will it send unzeroed application memory across like some other "fast" protobuf alternatives have done at the risk of data leaks?
I mean there's cap'n proto and flatbuffers already? Where's the benchmarks again capnproto in particular?
> In Bebop v3 you'll find that runtimes for TypeScript, Rust, and C# are much faster.
Sorry, but I would like some benchmark data to these claims....