Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://hachyderm.io/users/rain/statuses/111553584839677983">rain 🌦️ :verified_trans: (rain@hachyderm.io)'s status on Sunday, 10-Dec-2023 12:13:46 JST</a><a href="https://hachyderm.io/@rain" title="rain@hachyderm.io"><img src="https://gnusocial.jp/avatar/167473-48-20230903192522.webp" width="48" height="48" alt="rain 🌦️ :verified_trans:" style="position: absolute; left: 0; top: 0;">rain 🌦️ :verified_trans:</a></section><article><p>I refuse to believe this was written by actual practitioners in the field</p><p><a href="https://www.regulations.gov/comment/ONCD-2023-0002-0020" rel="nofollow noreferrer">https://www.regulations.gov/comment/ONCD-2023-0002-0020</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/2434145#notice-4813871">In conversation</a><time datetime="2023-12-10T12:13:46+09:00" title="Sunday, 10-Dec-2023 12:13:46 JST">about a year ago</time> <span>from <span><a href="https://hachyderm.io/@rain/111553584839677983" rel="external" title="Sent from hachyderm.io via ActivityPub">hachyderm.io</a></span></span><a href="https://hachyderm.io/@rain/111553584839677983">permalink</a><h4>Attachments</h4><ol><li><label><a rel="external" href="https://gnusocial.jp/attachment/1944513">C++ has made great strides in recent years in matters of resource and memory safety [P2687]. C++
benefits from having a formal specification, a fully-specified memory model, and an active community of
users and implementers. In contrast, some languages regarded as safe lack a formal specification, which
introduces its own safety concerns (e.g., how to ensure a consistent semantic view of code). These
important properties for safety are ignored because the C++ community doesn't have an organization
devoted to advertising. C++ is time-tested and battle-tested in millions of lines of code, over nearly half a
century, in essentially all application domains. Newer languages are not. Vulnerabilities are found with
any programming language, but it takes time to discover them. One reason new languages and their
implementations have fewer vulnerabilities is that they have not been through the test of time in as diverse
application areas. Even Rust, despite its memory and concurrency safety, has experienced vulnerabilities
(see, e.g., [Rust1], [Rust2], and [Rust3]) and no doubt more will be exposed in general use over time.</a></label><br><a href="https://media.hachyderm.io/media_attachments/files/111/553/581/104/478/253/original/aa06b1b4bfbc96d7.png" rel="external">https://media.hachyderm.io/media_attachments/files/111/553/581/104/478/253/original/aa06b1b4bfbc96d7.png</a></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
rain 🌦️ :verified_trans: (rain@hachyderm.io)'s status on Sunday, 10-Dec-2023 12:13:46 JST rain 🌦️ :verified_trans:
I refuse to believe this was written by actual practitioners in the field
https://www.regulations.gov/comment/ONCD-2023-0002-0020
In conversationabout a year ago from hachyderm.iopermalink
Attachments
1. C++ has made great strides in recent years in matters of resource and memory safety [P2687]. C++ benefits from having a formal specification, a fully-specified memory model, and an active community of users and implementers. In contrast, some languages regarded as safe lack a formal specification, which introduces its own safety concerns (e.g., how to ensure a consistent semantic view of code). These important properties for safety are ignored because the C++ community doesn't have an organization devoted to advertising. C++ is time-tested and battle-tested in millions of lines of code, over nearly half a century, in essentially all application domains. Newer languages are not. Vulnerabilities are found with any programming language, but it takes time to discover them. One reason new languages and their implementations have fewer vulnerabilities is that they have not been through the test of time in as diverse application areas. Even Rust, despite its memory and concurrency safety, has experienced vulnerabilities (see, e.g., [Rust1], [Rust2], and [Rust3]) and no doubt more will be exposed in general use over time.
  https://media.hachyderm.io/media_attachments/files/111/553/581/104/478/253/original/aa06b1b4bfbc96d7.png

Public

Embed Notice

HTML Code

Corresponding Notice