Conversation

I disagree. We still haven't succeeded in making memory safety considered a base foundation. People are still making new languages that aren't memory safe, and they're getting popular.

Quote Tweet

edef

@edefic

Jul 24, 2021

memory safety is not a big deal in the same sense that not dying from the black plague is not a big deal—you're probably going to have a hard time producing great works if it's a problem left unsolved, but it's also mere foundation

Show this thread

146

Replying to

i can think of … Jonathan Blow's language (which doesn't seem of sufficient importance to bother remembering the name), and … Nim?

Replying to

and

i thought nim was “as safe as rust” (e.g. has some mechanism for restricting/explicitly annotating i safety)?

Tony "Abolish ICE" Arcieri

Replying to

and

I hesitate to even opine on this topic as it seems hotly debated and I don’t really know anything about Nim, but I’ve seen this mentioned in the past github.com/nim-lang/Nim/w

Replying to

I think the issue is mostly around use-after-free and similar ways of invalidating other references to an object through one of the references.

10:21 PM · Jul 25, 2021Twitter Web App

Likes