# Incremental ports keep fast-moving products shipping

Markdown copy of https://realalpha.app/s/incremental-ports-keep-fast-moving-products-shipping/ on Real Alpha, the best minutes from long interviews with the people building AI. Cite and link the page, not this copy.

- Speaker: [Stephen Toub](https://realalpha.app/people/stephen-toub/) · Stephen Toub is a Distinguished Engineer at Microsoft.
- Host: [Ryan Peterman](https://realalpha.app/people/ryan-peterman/) · Host, The Peterman Pod · Went from new grad to staff engineer at Instagram in three years.
- Show: The Peterman Pod
- Episode: [Microsoft Distinguished Eng: Why And How To Port Your Entire Codebase to Rust | Stephen Toub](https://realalpha.app/v/PLMOVlZC4eU/), Nov 2, 2026
- Moment: 11:27 to 18:13 of the episode (7 min), playing on https://realalpha.app/s/incremental-ports-keep-fast-moving-products-shipping/; the episode from there: https://realalpha.app/v/PLMOVlZC4eU/?t=687

## Quote

> “we just incrementally moved the code base more and more from TypeScript to Rust in pieces in main, in the shipping code base, **shipping releases daily**.”
> — [Stephen Toub](https://realalpha.app/people/stephen-toub/) at [16:12](https://realalpha.app/v/PLMOVlZC4eU/?t=972) · The Peterman Pod

## Takeaways

1. Copilot shipped about 130 incremental releases during the port.
2. Fast-moving AI products can’t afford a long development freeze.
3. Temporary TypeScript-Rust interop peaked at several thousand signatures.

## About this segment

Stephen Toub explains why Copilot moved from TypeScript to Rust in small pieces rather than pausing for a full rewrite. The approach kept releases flowing and made the migration easier to validate.

From “Microsoft Distinguished Eng: Why And How To Port Your Entire Codebase to Rust | Stephen Toub”, Nov 2, 2026. [Watch the full episode](https://realalpha.app/v/PLMOVlZC4eU/)

## Transcript

Transcribed by machine (Whisper) from the episode’s audio, so a word may be off here and there.

[11:34](https://realalpha.app/v/PLMOVlZC4eU/?t=694) i wanted to ask you a little bit about the migration strategy because i've seen different strategies in different projects so for instance you mentioned bun earlier bun it looked like they kind of built up a giant basically a new branch that's just completely entirely in rust and then they shipped all in all at once uh stable rust release and they did it all in one one go whereas when i was reading what you had done it looked like a lot more incremental and little by little uh how did you think through the the different strategies and uh when might you select one versus the other the interesting thing about bun first i loved uh jared who wrote the the bun post i loved the post that he wrote it was really exciting because that post i wasn't aware that they were doing that port and then that post came out about

[12:27](https://realalpha.app/v/PLMOVlZC4eU/?t=747) halfway through our migration and it was really cool to see that this other project of approximately you know order of magnitude same amount of code it was in different language they were in zig rather than typescript but um that they had you know thought that this was a sensible thing to do and had landed it and in the post they talk about it taking i think 11 days for them to get to like 98 of their tests passing or something like that which is really cool and to your point like they They did it sort of in an en masse, like rewrite the world and go.

[13:01](https://realalpha.app/v/PLMOVlZC4eU/?t=781) It is interesting. I am not involved in the project, so I don't know all the details of what's going on behind the scenes. But it is interesting to me that if you look at their NPM page, they were shipping near daily builds. I think a lot of canary builds basically through mid-April, like for a long time, daily builds. And then mid-April, it stops. And then they talk about doing the 11 days of porting, which is an impressive feat to get from nothing to this, you know, a 500,000 line code base ported to Rust in 11 days and have a passing 98 or 99% of the test.

[13:43](https://realalpha.app/v/PLMOVlZC4eU/?t=823) But then they didn't have another NPM release of any kind, at least as far as I could see, for another two and a half months. um so there was this window where yes the the core port took a small period of time but it seems then like there was some aspect of stabilization and things like that happening such that there was this three month gap between releases um which interestingly is also approximately the same amount of time that it took copilot the other 14 and a half weeks that i spent uh porting copilot So, you know, there's lots of reasons why they differ, but fundamentally, it seemed to be about the same amount of time. And we just chose sort of different ways of going about it in the post. Jared makes a point about not wanting to do the incremental approach that co-pilot did because it would incur lots of temporary interrupt junk. And he's right. It did.

[14:41](https://realalpha.app/v/PLMOVlZC4eU/?t=881) um we just chose that approach knowing full well what we were getting ourselves into because of the sort of the constraints that we were under so uh you know for a javascript runtime um obviously fixing bugs and new features like that's all valuable um but you can pause for three months and the world isn't going to fall over right the javascript three months ago isn't all that different from JavaScript today. And you can do sort of a rewrite the world approach, pause everything, and then continue shipping when you're done.

[15:22](https://realalpha.app/v/PLMOVlZC4eU/?t=922) Agenda harnesses in the summer of 2026, if you pause for three months, the world you ship into will be very different from the worlds that you started in. And so trying to pause for, for a long period for you know a period of time even if it's a few days was not something that we were willing to entertain um and you know even if we've been able to do it in two weeks that would have been two weeks worth of either blocking the whole team or uh dealing with a constant influx of of changes Across a very large code base, and having to rationalize and, you know, all of those changes in and merge all those changes in as ports. Instead, we opted for the approach, which I think made sense for Copilot and made sense for Bon, where we just incrementally moved the code base more and more from TypeScript to Rust in pieces in main, in the shipping code base, shipping releases daily.

[16:30](https://realalpha.app/v/PLMOVlZC4eU/?t=990) And it's just that at the beginning, it was 100% TypeScript and 0% Rust. And at the end, it was 100% Rust and 0% TypeScript. And it was just, you know, more and more over time. And for the most part, it worked out quite well. It did mean that there was, to the point of the post, of the bun post, there was a lot of temporary code that came in and left. I think we were using NAPI RS for interop between TypeScript and Rust.

[17:00](https://realalpha.app/v/PLMOVlZC4eU/?t=1020) And at the peak point, we had several thousand interop signatures for, I think, two or three thousand for calling between them. And then by the end, it had dropped to zero because there was no more interop required. So for this project, it made a lot of sense. There are other approaches. You could do a rewrite the world. You could do, you know, have everyone stop what they're doing and just rewrite in main.

[17:27](https://realalpha.app/v/PLMOVlZC4eU/?t=1047) You could have a feature branch and allow main to keep going and then constantly be taking ports in. And for the incremental approach, you can do what we did, but rather than do the approach of what I chose, which was sort of atomically swap TypeScript with Rust, you could have sort of an A-B thing going where you have both the TypeScript and the Rust component And then you ship with both and you have a feature flag that allows you to ship between them and do sort of flights and experiments of those components side by side.

[17:57](https://realalpha.app/v/PLMOVlZC4eU/?t=1077) There are various reasons you might choose which. And I think what we chose ended up working out well for us, but all the other options would be valid or probably better for other projects.
