Tarpc: An RPC framework for Rust with a focus on ease of use (github.com)

30 points by peeyek 10y ago ↗ HN

10 comments

[ 4.5 ms ] story [ 37.0 ms ] thread

Interesting. While not an official Google product, this is in Google's GitHub repo. Seems to prove a nice validation of Rust's growing success.

haneefmubarak 10y ago ↗

Does anyone know what the usage of Rust is like inside Google? Is there strong pressure to use Go for all new projects, btw?

nostrademons 10y ago ↗

Most of my Googler friends had never heard of it (I've mentioned I've been playing around with it for a project lately). I imagine that it's like any large tech company with a well-educated workforce: you'll have some folks who like to keep up-to-date with the latest tech and try it out in side projects. Even Haskell had a few passionate supporters while I was at Google.

When I left 2 years ago, there was no "pressure" to use Go for new projects but a number of projects were adopting it anyway, since it had been blessed with "official language" status and a lot of Google infrastructure worked with it.

eximius 10y ago ↗

It does seem easy to use, I'll give them that! :)

euyyn 10y ago ↗

What's the wire protocol used?

haneefmubarak 10y ago ↗

From looking through the source (mind you, I don't code in Rust, so I might be totally wrong) it looks like they used the serde crate for some stuff but mostly rolled out their own.

cetra3 10y ago ↗

Serde https://github.com/serde-rs/serde serialization with Bincode https://github.com/TyOverby/bincode

dozzie 10y ago ↗

What a shame. It renders Tarpc next to useless, since it won't talk to anything that is not Rust.

euyyn 9y ago ↗

Shameless plug: Why not talk the gRPC protocol? :)

xuejie 10y ago ↗

I'm not sure how practical this can be, one advantage of having an RPC, is that it allows for cross-language communication.

In this case, won't it be nicer to invest in a rust port of grpc instead of building this?