grpc-rust

This is nice double entendre because tonic is a pleasant gRPC server library in rust! https://github.com/hyperium/tonic

Are the benchmarks actually fair? See: https://github.com/apache/fory/blob/fd1d53bd0fbbc5e0ce6d53ef... It seems if the serialization object is not a "Fory" struct, then it is forced to go through to/from conversion as part of the measured serialization work: https://github.com/apache/fory/blob/fd1d53bd0fbbc5e0ce6d53ef... The to/from type of work includes cloning Strings: https://github.com/apache/fory/blob/fd1d53bd0fbbc5e0ce6d53ef... reallocating growing arrays with collect: https://github.com/apache/fory/blob/fd1d53bd0fbbc5e0ce6d53ef... I'd think that the to/from Fory types is shouldn't be part of the tests. Also, when used in an actual system tonic would be providing a 8KB buffer to write into, not just a Vec::default() that may need to be resized multiple times: https://github.com/hyperium/tonic/blob/147c94cd661c0015af2e5...

I wonder how hard it would be to make the Tonic [1] Rust GRPC implementation target Workers. Maybe it's too tied to the Tokio runtime. [1]: https://github.com/hyperium/tonic

> Where are the pervasively used compression libraries in Rust? Video and audio codecs? Network stacks? Database engines? System management utilities? PKI and encryption stacks? All that stuff is still in C. After ten years of Rust success! It's not ten or 20 years, the first release of Rust was in 2015. Pre-1.0 Rust was a wildly different language, with green threads, segmented stacks, regular and wild breakage, not really a C replacement! Please understand this point. But anyway here are some projects: https://github.com/ctz/rustls a TLS library that uses https://github.com/briansmith/webpki a pki library https://github.com/burntsushi/rust-snappy a compression library https://github.com/tikv/tikv a database engine https://github.com/hyperium/tonic a gRPC library https://github.com/tock/tock an embedded OS https://lib.rs/command-line-uti