Performance of Rust Language [pdf]

A new talk about Rust, the programming language famous for trying to stop dangerous memory mistakes, asked the question that always starts a nerd food fight: how much speed do you lose for safety? The headline answer from the slides seems fairly mild — around 3% slower on average, with some uglier cases reaching 15% compared with C++ — but the community reaction instantly turned that into a full-blown comment-section cage match. One reader basically translated the whole deck into a single line: so safety costs a few percent, worst case more? And that simple framing became the battleground.

From there, the hot takes rolled in. One camp said this is basically fine, with one commenter bluntly declaring Rust is about as fast as C, while claiming modern C++ still pulls ahead. That’s the kind of statement that lands like a lit match in a room full of benchmark charts. Another group was less focused on who “wins” and more annoyed that Rust still misses easy speed-ups in places where the compiler could, in theory, be smarter. Translation for normal humans: some people think Rust is still leaving performance on the table because its internal machinery is messy and evolving.

The funniest energy came from the ultra-detailed nitpicks. One commenter dove into a tiny loop example to argue the compiler should see a crash coming before the loop even starts — peak internet behavior, and exactly the kind of obsessive debate these posts live for. Meanwhile, another wanted version-by-version charts because a single snapshot wasn’t juicy enough. In other words: the talk was about performance, but the real show was the community doing what it does best — arguing over single-digit percentages like civilization depends on it.