Public
- Public
- Network
- Groups
- Featured
- Popular
- People

Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://minidisc.tokyo/notes/9qc1az6nlq">SuperDicq (superdicq@minidisc.tokyo)'s status on Friday, 01-Mar-2024 18:46:49 JST</a><a href="https://minidisc.tokyo/@SuperDicq" title="superdicq@minidisc.tokyo"><img src="https://gnusocial.jp/theme/gnusocialjp/default-avatar-stream.png" width="48" height="48" alt="SuperDicq" style="position: absolute; left: 0; top: 0;">SuperDicq</a><div><a href="https://freesoftwareextremist.com/objects/42fea3b2-a4b9-45ad-9dcd-b4c8884d1128" rel="in-reply-to">in reply to</a><ul><li></ul></div></section><article><p><a href="https://freesoftwareextremist.com/users/Suiseiseki">@Suiseiseki@freesoftwareextremist.com</a> Personally I think memory safety is not an issue that should be fixed by the programming language per se. <br><br>You can totally write perfect memory safe C code, if you can't do that it's just a skill issue amirite?</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/2776723#notice-5508240">In conversation</a><time datetime="2024-03-01T18:46:49+09:00" title="Friday, 01-Mar-2024 18:46:49 JST">about 8 months ago</time> <span>from <span><a href="https://minidisc.tokyo/notes/9qc1az6nlq" rel="external" title="Sent from minidisc.tokyo via ActivityPub">minidisc.tokyo</a></span></span><a href="https://minidisc.tokyo/notes/9qc1az6nlq">permalink</a></footer></blockquote>

Corresponding Notice

Embed this notice
SuperDicq (superdicq@minidisc.tokyo)'s status on Friday, 01-Mar-2024 18:46:49 JSTSuperDicq
in reply to
- 翠星石
@Suiseiseki@freesoftwareextremist.com Personally I think memory safety is not an issue that should be fixed by the programming language per se.

You can totally write perfect memory safe C code, if you can't do that it's just a skill issue amirite?
In conversationabout 8 months ago from minidisc.tokyopermalink

Public

Embed Notice

HTML Code

Corresponding Notice