Memory Safety is a Red Herring (steveklabnik.com)

submitted 11 months ago by lysdexic@programming.dev to c/rust@programming.dev

49 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] noctisatrae@beehaw.org 4 points 11 months ago

TL;DR Linkedin clickbait

I did read the article and it’s maybe it’s just me being a bitter, spiteful & petulant being, obnoxious to talk with but this article sucked. Every point ranged hollow.

It was really bad because the author in his 11y of writing Rust never once heard about the philosophy of Rust/Unsafe Rust.

The goal of MSLs is to reduce UB, and Rust want to do that but keep the speed and the productivity.

Of course, at some point you may need some C/C++ because it’s the cornerstone of modern programming but what you are calling with FFI are audited, open-source libraries so memory leaks/undefined behaviour is minimised.

Rust is implemented in Rust so FFI is greatly minimised if we follow the logic of the blogger.

[-] BatmanAoD@programming.dev 6 points 11 months ago

the author in his 11y of writing Rust never once heard about the philosophy of Rust/Unsafe Rust.

Are you...aware of who the author is? He literally co-wrote The Book, aka The Rust Programming Language.

[-] lysdexic@programming.dev 4 points 11 months ago

It was really bad because the author in his 11y of writing Rust never once heard about the philosophy of Rust/Unsafe Rust.

You're talking about Steve Klabnik, a guy known for being one of the authors of The Rust Programming Language and the guy who literally ran the @rustlang Twitter account.