Why I built it
Too many RPC frameworks optimize for abstraction purity while making the operational story worse. Quill is an attempt to be more pragmatic: keep protobufs central, make transport decisions adaptive, and treat failure semantics as part of the developer interface rather than an afterthought.
What it does
Quill is a modern RPC framework written in Rust. It supports adaptive transport through "Prism profiles", automatically selecting between HTTP/1.1, HTTP/2, and HTTP/3 over QUIC based on the environment. Error handling uses RFC 7807 Problem Details so failures travel as real HTTP responses instead of a 200 OK envelope carrying bad news.
The project also includes a custom streaming layer with flow control, a tensor streaming crate for ML inference workloads, and Python bindings through PyO3. A single CLI handles code generation, RPC calls, and benchmarking.
Why it matters
Framework work is useful because it forces design choices into the open. You have to decide what the common path should feel like, which tradeoffs deserve escape hatches, and how much complexity the user should be asked to carry. That is the same judgment I care about in AI systems work.