News for hackers. Stuff that matters.
Re:C++ Frequently Questioned Answers (2009) by pcwalton on Monday January 24, 2022 @02:49PM (#30062974)
> Put simply, the extra work to satisfy the borrow checker prevents errors they do not make.

> This contradicts Rust propaganda, where a few CVE numbers are cited over and over, echo-chamber style. What these citations never mention is that they are for bugs in mostly very old code.

Empirically this is not true. https://twitter.com/LazyFishBarrel/ is not citing "a few CVE numbers over and over"; for example, in browsers, new code is disproportionately responsible for vulnerabilities. I know most of the people at the big tech companies doing the research into where the security problems in major C++ software come from; they're not making the results up.

Re:C++ Frequently Questioned Answers (2009) by ncmncm on Monday January 24, 2022 @07:11PM (#30066041)
When I look into these CVEs and see "use after free", I know immediately it is not a problem in modern code.