Here is my canonical DHH/Rust take: Because it was stringly typed, interpreted at runtime and could be monkey patched (like random files could change the behaviour of any other class, crazy stuff), most Ruby on Rails apps back in the day had to have something like 500% test coverage, genuinely insane test suites that acted as a compiler and took hours to run. Inverted Testing Pyramid basically. Gherkin/Cucumber was popular to these people, wRiTe TeSTs In EnGlIsH etc. No wonder that kind of thing appeals to the ‘dark factory’ ‘don’t look at the code’ types. Who cares about an elegant type safe representation of your business domain so clearly written an expert can verify just by reading it if the 3000 markdown files check out and a 7 hour browser clicking test suite passes. Rust is better than Ruby for AI slopcannons because Rust is statically typed. DHH has just discovered typing and compile time checking. He’ll still need a very large test suite to handle the AI slot machine but can save quite of a bit of effort compared to a vibe coded Ruby equivalent.

If you can’t read the code how are you going to resolve merge conflicts lol

“Just one engineer” was Stephen Toub who is basically a god amongst men as far as developers go

Ted's Tech "Show" Episode 11 - The Copilot to Rust port - has Microsoft abandoned C# & .NET? 0:00 Intro 0:24 The Copilot Rust Migration 1:03 Community reaction 1:46 Architectural concerns 2:23 Rationale for choosing Rust 3:13 C# and native AOT capabilities 3:57 Performance and validity 4:23 AI generation and error analysis 5:33 Microsoft's broader rust adoption 6:47 Closing thoughts and critique