If you read it carefully you'll see that they "rewrote" it by replacing components of it. Which: 1. Allowed them to evaluate if it would actually work. 2. Allo

If you read it carefully you'll see that they "rewrote" it by replacing components of it. Which: 1. Allowed them to evaluate if it would actually work. 2. Allowed them to train the team on it in a scalable way. The result is that the team learned Rust and Rust fixed a bunch of problems. They were appropriately pragmatic in their approach and Rust was appropriately pragmatic in it's solutions to their problems. If you are ever considering migrating your codebase for some reason this is how you should go about it. TLDR: You are heavily mis-characterizing their team and this article.