Gergely Orosz · 6 min read · Product Discovery
Why Rust is different, with Alice Ryhl
Read the original on newsletter.pragmaticengineer.com →
On The Pragmatic Engineer Podcast, host sits down with Alice Ryhl to discuss what makes Rust different from TypeScript, Go, and C++. The episode covers memory safety, ownership, unsafe Rust, Cargo, RFC-driven governance, six-week release cycles, and Rust’s growing use in the Linux kernel.
Key Takeaways
- Open source contributions can open career doors, as Alice landed a Google job and became a Tokio maintainer through community work.
- Reliability is a strong backend pitch for Rust over TypeScript, emphasizing safer backend development and fewer runtime errors.
- Rust over C++ can reduce security vulnerabilities thanks to memory safety, with unsafe Rust as a considered exception.
- Rust turns implicit failures into compile-time errors, enforcing checks for nulls, uninitialized variables, and error propagation with the '?' operator.
- The hardest part of learning Rust is data structure design due to the ownership model, with challenges around cyclic graphs and compiler constraints.
Excerpt
Stream the latest episode Listen and watch now on YouTube , Spotify , and Apple . See the episode transcript at the top of this page, and timestamps for the episode at the bottom. Brought to You by • Antithesis – if you write Rust code, check out Hegel-Rust : a free, open-source property-based testing library for Rust, built by the team behind Hypothesis. It’s now maintained by Antithesis . If you try Hegel and like it, your Hegel tests will run in Antithesis as written, as well. • Sentry – application monitoring software built by developers, for developers. I’ve…