Apr 15
Loading video player...
Rust has been the most admired language on Stack Overflow for 9 years straight. Discord, Microsoft, AWS, and Google all bet on it — and got remarkable results. But in 2025, the TypeScript team looked at Rust and said no thanks, we're going with Go. So which is it? After 6 months of real Rust projects, I have an honest answer. This is not a beginner tutorial and not a hype piece. It's a direct look at what Rust actually does well, where it genuinely fails the cost-benefit test, and how to tell whether it belongs in your stack. We cover the borrow checker and why it is more clever than annoying once it clicks, a real comparison against C, C++, Go, and Zig, the Discord and Dropbox rewrites and what they actually prove, the TypeScript team's rejection and why Anders Hejlsberg's reasoning is the most useful thing written about Rust in years, the learning curve data from Rust's own community survey, and a final verdict with a clear framework for your own decision. If you are writing Rust or considering it, the next video covers a structured AI-assisted development workflow — plan-first, rules-based, and specifically useful when your feedback loop is already slowed by compile times. Leave a comment with what you are building — and whether Rust made the shortlist. #Rust #rustlang #softwareengineering #systemsprogramming #rustprogramming