Chris Sawyer really went off the deep end after programming RCT in assembly.

What. The. Fuck.

Amazing

I mean yes, I do, given safe Rust inherently fixes seemingly every exploit listed in this article:

• ~~RCE from integer overflow (not possible by default in Rust, CVSS 9.0)~~
• RCE from a race condition (not possible in safe Rust, CVSS 9.0)
• An exploit of a buffer copy
• An out-of-bounds write leading to local privilege escalation
• Using an uninitialized resource
• TCP query stack buffer overflow leading to local privilege escalation

I feel like it's the 1960s and I'm being told "we get it, you like seatbelts".

Edit: Sorry, re: the first one. I was misremembering based on a mix of a few things (see below). It does this in debug mode (which in itself is good to have), and it won't compile if it can detect an overflow statically, but it's not checking over/underflow at runtime by default. It can do this if you want it to, but that's an inherent speed penalty from C. I was thinking of Swift, which does automatically detect integer under/overflow at runtime unless you explicitly tell it not to on a per-operator basis.

In the spirit of not making you "trust me bro" since I was so wrong about the integer under/overflow one, here's Rust's overview of how safe Rust guarantees against data races.