podcasts / Ryan Peterman / episode / question
Question

Why did Stephen Toub choose Rust over C#, Go or Java for the Copilot runtime?

Answered from Microsoft Distinguished Eng: Why And How To Port Your Entire Codebase to Rust | Stephen Toub · Ryan Peterman · 2026-11-02

Stephen Toub had agents build small prototypes of five to ten thousand lines each in TypeScript, Python, Go, C#, Java and Rust, then measured performance, working set, throughput and embeddability. TypeScript and Python dropped out quickly, Go was fast but not designed for interop, and Java was only okay. C# with native AOT and Rust were roughly tied, so softer factors decided it: GitHub has more Rust projects and more engineers who know Rust.

Source: our own transcription of the episode. The full conversation is on Ryan Peterman (2026-11-02). Read the whole episode summary →

▸More from this episode

Q1Why did Stephen Toub rewrite the GitHub Copilot runtime from TypeScript to Rust?Q3How did Stephen Toub's incremental Copilot port compare with Bun's big-bang Rust rewrite?Q4How did Stephen Toub catch regressions when AI agents ported the Copilot codebase to Rust?Q5What did Stephen Toub say about AI agents changing tests to make code pass?Q6How did Stephen Toub review hundreds of thousands of lines of AI-written code?Q7How much did Stephen Toub's AI-driven Copilot Rust port cost in tokens and time?Q8How does Stephen Toub decide whether a codebase rewrite or migration is worth doing?
Transcribe your links. Paste a YouTube, Google Drive or podcast link and WhipScribe gives you the transcript. Transcribe a link →