riegeli
quick-protobuf
| riegeli | quick-protobuf | |
|---|---|---|
| 1 | 3 | |
| 414 | 446 | |
| 1.0% | - | |
| 9.5 | 6.3 | |
| 3 days ago | 8 months ago | |
| C++ | Rust | |
| Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
riegeli
-
Add extra stuff to a “standard” encoding? Sure, why not
> didn’t find any standard for separating protobuf messages
The fact that protobufs are not self-delimiting is an endless source of frustration, but I know of 2 standards:
- SerializeDelimited* is part of the protobuf library: https://github.com/protocolbuffers/protobuf/blob/main/src/go...
- Riegeli is "a file format for storing a sequence of string records, typically serialized protocol buffers. It supports dense compression, fast decoding, seeking, detection and optional skipping of data corruption, filtering of proto message fields for even faster decoding, and parallel encoding": https://github.com/google/riegeli
quick-protobuf
-
Fivefold Slower Compared to Go? Optimizing Rust's Protobuf Decoding Performance
[quick-protobuf]: https://github.com/tafia/quick-protobuf
-
Add extra stuff to a “standard” encoding? Sure, why not
I actually went through all projects listed in [1] because I remember this very quirk. It turns out that there are many such libraries that have two variants of encode/decode functions, where the second variant prepends a varint length. In my brief inspection there do exist a few libraries with only the second variant (e.g. Rust quick-protobuf), which is legitimately problematic [2].
But if the project in question was indeed protobuf.js (see loeg's comments), it clearly distinguishes encode/decode vs. encodeDelimited/decodeDelimited. So I believe the project should not be blamed, and the better question would be why so many people chose to add this exact helper. Well, because Google itself also had the same helper [3]! So at this point protobuf should just standardize this simple framing format (with an explicitly different name though), instead of claiming that protobuf has no obligation to define one.
[1] https://github.com/protocolbuffers/protobuf/blob/main/docs/t...
[2] https://github.com/tafia/quick-protobuf/issues/130
[3] https://protobuf.dev/reference/java/api-docs/com/google/prot...
[4] https://github.com/protocolbuffers/protobuf/blob/main/src/go...
What are some alternatives?
msgpack - MessagePack is an extremely efficient object serialization library. It's like JSON, but very fast and small.
nix-init - Generate Nix packages from URLs with hash prefetching, dependency inference, license detection, and more [maintainer=@figsoda]
protobuf-conformance - A repository running the Protobuf conformance tests against various libraries
imstr - Immutable strings, in Rust.
Protobuf - Protocol Buffers - Google's data interchange format
ntfy - Send push notifications to your phone or desktop using PUT/POST
protobuf - Protocol Buffers for JavaScript & TypeScript.
flapigen-rs - Tool for connecting programs or libraries written in Rust with other languages
inkwell - It's a New Kind of Wrapper for Exposing LLVM (Safely)