After Watching Fireship's Rust in 100 Seconds: My Take
I watched Fireship's 'Rust in 100 Seconds' this morning. It does what Fireship does best: pack a decade of language design decisions into under two minutes. Here's what it got right, what it missed, and what production experience adds to the picture.
I Just Watched Fireship's Rust in 100 Seconds
I just watched Fireship's Rust in 100 Seconds and my first reaction was: best possible intro that will also get the most people in trouble. Not because it's wrong. Because it's right in ways that make beginners overconfident.
What the Video Actually Covers
Fireship walks you through ownership, borrowing, and lifetimes in rapid succession. That's the right order because that's the order the Rust compiler will destroy your confidence in. The video frames Rust as a systems language achieving memory safety without a garbage collector. One value, one owner, memory freed when the owner goes out of scope. No GC polling. No reference counting overhead by default. The pitch is accurate and the video delivers it cleanly.
The visuals illustrating the borrow checker are genuinely good. Fireship also correctly identifies the learning curve as steep without sugarcoating it. If you watched expecting Rust to feel like TypeScript with angle brackets, you are going to have a bad time.
What the Video Got Right
Here's the thing: the borrow checker framing is exactly correct. Rust's compiler is code review that never gets tired and never approves a use-after-free because it was rushing. We had a memory corruption bug at Netflix in 2018 that took a senior engineer four days to find in a C++ service. A Rust compiler rejects that code before it ever runs. The pain is the point.
What the Video Missed
Fireship's 100 seconds can't cover everything. But here's what I'd add.
- Async Rust is a different language. Ownership gets significantly more complicated with futures and Tokio. Most real-world Rust pain in 2024 lives here. The video doesn't touch it.
- Compile times are a real operational cost. At scale, Rust builds take minutes. That's the price of the borrow checker's guarantees and you need to budget for it.
- Safe Rust versus unsafe Rust. The safety guarantees Fireship describes apply to safe Rust. Unsafe blocks exist, they're necessary for FFI, and they hand you a loaded gun with no safety. Don't do this: drop an unsafe block because the borrow checker annoyed you. I've seen this kill production.
What to Do After Watching
- Read the Rust Book at doc.rust-lang.org. All of it. Fireship's video is the trailer. The Rust Book is the film.
- Do Rustlings. Small exercises targeting exactly the concepts the video describes.
- Learn synchronous Rust until the borrow checker stops feeling hostile. Then introduce Tokio. Not before.
Should You Watch It?
Yes. It's 100 seconds. Fireship's video is for anyone who has never heard of Rust and wants to know if it's worth their attention. It is not a tutorial and it doesn't pretend to be. Watch it, then go read the Rust Book, then write ten thousand lines of Rust. The video is the door. Walking through it is on you.