Gergely Orosz

But in Rust, you cannot do that either, right?

I get a sense that the language designers have thought really hard of what are ways that typically go wrong in a lot of other programming languages, and they just try to fix it through the compiler.

The documentation example is the one where I'm still like, wow.

It happens all the time.

You have a comment, example or not, and then it gets out of sync, and we always complain about this, and we don't know how to fix it.

I know I've been complaining for a decade plus,

Rust is the first language where I hear an actual solution, even if it's not a perfect one.

And we've had the pitch from TypeScript or similar languages.

What about the pitch from C++?

Let's talk about memory safety.

Okay.

And then an attacker who figures this out could populate something there, eventually get that code somehow executed or configuration read, and then boom.

That's a root user.

And then once an attacker manages to do that, they can take over the...

Whatever your server or whatever is running.

And then, of course, from there on, it can just spiral out of control, right?

Once you're root, you're lost.

Yeah.

Do I understand that a very strong pitch of Rust, especially coming from C++, is memory safety eliminates this whole class of bugs, which can turn into security vulnerabilities, which are one of the most serious threats any software can have.

MARTIN SPLITT- That is a pretty good pitch.