Google really dropped the ball with protobuf when they took so long to make them zero-copy. There are 3rd party implementations popping up now and a real risk of future wire-level incompatibilities across languages.
jeffbee 32 minutes ago [-]
"zero copy" in this context just means that the contents of the input buffer are aliased to string fields in the decoded representation. This is a language-level feature and has nothing to do with the wire format.
slipknotfan 3 days ago [-]
Commonly used crates should be blessed and go into an extended stdlib.
josephg 1 hours ago [-]
Ok, but this is not a commonly used crate. Its brand new!
alfiedotwtf 13 minutes ago [-]
Unless there’s a strict schedule for review to remove them, please no… because that’s how we get BerkeleyDB and CGI in the standard Perl libraries.
If anything, there should be “less than blessed” “*-awesome” libraries
echelon 34 minutes ago [-]
No HTTP, Proto, or gRPC crate should ever find itself in the stdlib.
Didn't we learn this with python?
How many python http client libraries are in the dumping ground that is the python "batteries included" standard library?
And yet people always reach for the one that is outside stdlib.
Valodim 8 minutes ago [-]
You don't think golang's http library is a good idea? I would have thought everyone is happy we have it
Rendered at 06:59:27 GMT+0000 (Coordinated Universal Time) with Vercel.
If anything, there should be “less than blessed” “*-awesome” libraries
Didn't we learn this with python?
How many python http client libraries are in the dumping ground that is the python "batteries included" standard library?
And yet people always reach for the one that is outside stdlib.