Zero-copy protobuf and ConnectRPC for Rust

Anthropic just dropped two Rust goodies: “buffa” for faster, low-copy Protocol Buffers (the binary format lots of apps use to talk) and “connect-rust,” a server that speaks multiple styles of remote calls (Connect, gRPC, and gRPC‑Web) on the same code. It’s already running in production, passes mountains of tests, and—plot twist—was built in six weeks with heavy AI help. The post promises fewer copies of data and fewer memory hiccups. The comments? Absolute fireworks.

One camp wants the Rust world to bless it as standard so everyone can stop reinventing the wheel. The blame brigade drags Google for moving slowly—“dropped the ball” and now there’s “risk of incompatibilities” if everyone builds their own. Meanwhile, battle-scarred engineers share horror stories about today’s Rust gRPC stack misbehaving behind load balancers—think servers throwing tantrums when traffic is retried—begging this new stack to save them. The pedants pounce: “not true zero-copy,” more like fewer allocations; if you want real zero-copy nirvana, try FlatBuffers. And then there are the tinkerers flexing their own “zero-copy-ish” libs, cheering the push for less memory churn. Verdict: big promise, bigger expectations—and the crowd’s split between “ship it,” “Google fix it,” and “it’s not really zero, bro.”