News for hackers. Stuff that matters.
Re:C meeting is over. C23 added: by drran on Saturday February 19, 2022 @07:25AM (#30396612)
Majority of CVE's are because of C memory model, which is fixed in modern languages. C memory model is the constant source of vulnerabilities, thus it better to write new code in a memory safe language, like Rust.
Re:C meeting is over. C23 added: by masklinn on Saturday February 19, 2022 @10:11AM (#30397678)
> Majority of CVE's are because of C memory model

“Memory safety” (or lack thereof) is probably less ambiguous: usually “memory model” is the interaction between program and memory, specifically as it pertains to concurrency. And in the latter understanding I believe C has about the same model as C++, which is also the one adopted by Rust. And while it’s fiddly, it’s not a complete disaster.

Re:C meeting is over. C23 added: by moralestapia on Saturday February 19, 2022 @09:59AM (#30397580)
>Majority of CVE's are because of C memory model

I haven't checked that but I believe you. My only nitpick is that I wouldn't put the whole blame for that on C, as there are proper ways to produce "safer"[1] code. What other languages did was lower the entry barrier to write better code, but that doesn't mean one language is inherently better that another.

1: No code is ever safe, not even formally verified code.

Re:C meeting is over. C23 added: by phendrenad2 on Saturday February 19, 2022 @05:33PM (#30401165)
C and Rust have the same memory model though, unless you're using a definition of "memory model" that I'm unaware of.
Re:C meeting is over. C23 added: by pkrumins on Saturday February 19, 2022 @07:45AM (#30396725)
Rust is a syntax error, not a programming language.
Re:C meeting is over. C23 added: by DrMeepster on Monday February 21, 2022 @11:58PM (#30424148)
what does this mean? It sounds like you tried to make a funny programming insult, but it fell flat if that's what you were going for