protobuf-conformance
protobuf
| protobuf-conformance | protobuf | |
|---|---|---|
| 1 | 18 | |
| 20 | 9,663 | |
| - | 0.7% | |
| 8.4 | 4.6 | |
| 13 days ago | 5 days ago | |
| JavaScript | JavaScript | |
| Apache License 2.0 | GNU General Public License v3.0 or later |
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.
protobuf-conformance
-
Add extra stuff to a “standard” encoding? Sure, why not
It looks like Protobuf actually has a test suite to ensure compliance with the protocol:
https://github.com/bufbuild/protobuf-conformance
Seems like a good idea for protocols in general to have an official test suite, as a way to address this problem
protobuf
- Eval("quire".replace(/^/,"re"))(moduleName)
-
How we reverse-engineered Google Maps pagination
Google Maps URLs contain the pb parameter contains string-encoded Protobuf. The format is the same as for the data parameter in the browser URL on Google Maps. It contains !-separated values. There are several answers on StackOverflow, gists on GitHub, some blog posts about decoding, and even a kinda official guide on reverse engineering protobuf, but none of this touches pagination.
-
Add extra stuff to a “standard” encoding? Sure, why not
Seems like protoduf.js has the exact same methods as Google’s implementations with the same names (encode/decode to not prepend with length, encodeDelimited/decodeDelimited for prepending length). It is hard for me to say they’re adding to the standard when they’re just replicating Google’s libraries.
https://github.com/protobufjs/protobuf.js#toolset
-
Question about compressing JSON in multiplayer position updates
If it really is a problem, then another option is to use Protobus or Message Pack for serializing (maybe into base64?).
-
Looking for ideas on how to implement serialization and deserialization between C++ and Javascript
I use protocol buffers. protobufjs translates into json.
-
GRPC Gateway API Client?
I have tried GRPC gateway generation tools: - PBJS: https://github.com/protobufjs/protobuf.js/
- Protobuf-ES: The Protocol Buffers TypeScript/JavaScript runtime we all deserve
- Did I understand the basic concept of website development with Node Js correctly?
- how can i use protobuf with sveltekit, please?
-
is there any startup or famous web app using grpc/grpc-web for their frontend
We use https://github.com/improbable-eng/grpc-web for the server part with https://github.com/protobufjs/protobuf.js on the frontend.
What are some alternatives?
msgpack - MessagePack is an extremely efficient object serialization library. It's like JSON, but very fast and small.
snappy - DEPRECATED - please use https://github.com/Brooooooklyn/snappy. Nodejs bindings to Google's Snappy compression library
riegeli - Riegeli/records is a file format for storing a sequence of string records, typically serialized protocol buffers.
pbf - A low-level, lightweight protocol buffers implementation in JavaScript.
material-ui - MUI Core (formerly Material UI) is the React UI library you always wanted. Follow your own design system, or start with Material Design. [Moved to: https://github.com/mui/material-ui]
compactr - Schema based serialization made easy
Protobuf - Protocol Buffers - Google's data interchange format
Vicis - Presentation and transformation layer for data output in RESTful APIs.
TypeScript - TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
material-ui - MUI Core (formerly Material UI) is the React UI library you always wanted. Follow your own design system, or start with Material Design. [Moved to: https://github.com/mui/material-ui]
Cap'n Proto - Cap'n Proto serialization/RPC system - core tools and C++ library