Folks, as MCP’s language ecosystem expands, we’re spending more time re‑implementing the same deterministic‑state logic than shipping new ideas. I’d like us to flip that ratio by standardizing on a single, battle‑hardened Rust core (rust‑sdk) that owns the heavy workflow engine— sessions, peering, transport, serialization—while each language surface (Python, JS/TS, Go, etc.) stays 100 % idiomatic and lightweight.
Rust gives us memory‑safe, no‑GC performance overhead, a stable FFI, and a proven path. The payoff is immediate: one quality, security and performance audit instead of five, feature parity across languages on day 1, and p99 latencies that drop from milliseconds to microseconds—without asking Python or JavaScript developers to learn Rust.
In short, one deterministic engine, many friendly faces. We have built a V 0.1 Python SDK based on this architecture so that we write less boilerplate and innovate faster on the parts that matter.
tarun_anand|9 months ago
Rust gives us memory‑safe, no‑GC performance overhead, a stable FFI, and a proven path. The payoff is immediate: one quality, security and performance audit instead of five, feature parity across languages on day 1, and p99 latencies that drop from milliseconds to microseconds—without asking Python or JavaScript developers to learn Rust.
In short, one deterministic engine, many friendly faces. We have built a V 0.1 Python SDK based on this architecture so that we write less boilerplate and innovate faster on the parts that matter.