LOADING
This talk puts popular Rust rewrites to the test. We'll examine how these tools stack up against their battle-tested predecessors, looking at real-world performance, compilation times, binary sizes, feature completeness, and ecosystem maturity.
The Rust ecosystem loves to claim tools are 🚀 blazingly fast 🚀, and the "Rewrite It In Rust" movement has given us alternatives to everything from CLI utilities to web servers. But are these replacements actually faster? Or is the RIIR movement more about memory safety theater than real performance gains?
This talk puts popular Rust rewrites to the test. We'll examine how these tools stack up against their battle-tested predecessors, looking at real-world performance, compilation times, binary sizes, feature completeness, and ecosystem maturity. Some Rust tools genuinely deliver on their promises—but others might be solving problems that don't exist. Whether you're a RIIR evangelist or a skeptic, you'll walk away with data-driven insights into when Rust replacements make sense and when the original is still the better choice. Expect honest assessments, performance comparisons, and maybe fewer rocket emojis.
During this talk we'll build a basic, working async runtime using nothing more than a standard library. The point? To see it's approachable for mere mortals.
In this introductory talk, we will explore what it means to "Ratatuify" the Rust package manager, Cargo.
The talk explores how Rust’s type system and memory safety can be leveraged to enforce mandatory guardrails at the infrastructure level, where traditional frameworks often fall short.
For infrastructure engineers, SREs, platform teams, and Rust developers who've felt the pain of configuration drift, failed deployments, and infrastructure code that simply doesn't scale safely.
In 2024, I added the `Option::as_slice` and `Option::as_mut_slice` methods to libcore. This talk is about what motivated the addition, and looks into the no less than 4 different implementations that made up the methods. It also shows that even without a deep understanding of all compiler internals, it is possible to add changes both to the compiler and standard library.
