Unleashing 🦀 The Ferris Within
summary
Microsoft ports DirectWrite core and ports parts of GDI to Rust, Windows boots with the Rust GDI pieces and all GDI tests pass while microbenchmarks show equal or better performance; memory safety still drives ~60–70% of native CVEs so efforts combine CodeQL and memory tagging with static/dynamic analysis and sanitizer tooling; interop remains the pain point with lots of unsafe bridging that shrinks as more code moves to Rust and teams contribute fixes upstream while using the windows crate and automated dependency scoring to gate production use.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:37Why teams choose Rust
- 10:09Memory safety in C++
- 15:54Hardening C++ with tooling
- 22:16Safer systems priorities
- 29:26Azure security evolution
- 32:23Rust in Windows cases
- 43:25Learning Rust onboarding
- 48:42Rust and C++ interop
- 53:31Rust dependency management
related talks
36mUnleashing 🦀 The Ferris Within
35mMicrosoft is Getting Rusty: A Review of Successes and Challenges
31m"From Blue Screens to Orange Crabs: Microsoft’s Rusty Revolution"
45mRust
21mRust - Cargo Cult?
06mRust (in production) Without Fear
40mWhat's up with Rust?
58mC# and Rust: combining managed and unmanaged code without sacrificing safety