[pron]

So that could be a clear definition, but for it to be "table stakes" it needs to have some universal value and it doesn't (in fact, that very same definition could also classify even C as "memory safe"): https://news.ycombinator.com/item?id=49087458

[steveklabnik]

I can say that something is "table stakes" for me without demanding that everyone else adhere to my values.

[justrust]

Please k*ll yourself, mentally ill pedophile Steve Klabnik.

[awesome_dude]

There's little point in me telling the world how I like my dinnercooked, unless the world both understands exactly what I mean, and cares

[IshKebab]

I'm not exactly sure what you mean by "universal value", but I would say to be "table stakes" (i.e. not optional), it has to have overwhelming value. I think outside some fairly niche areas (e.g. programs that don't process untrusted data at all), it very very clearly has overwhelming value.

Now you might argue that the other features of Zig, like `defer`, are so good that they reduce the chance of memory errors and therefore memory safety has less value for Zig. But that seems highly dubious to me, especially for use-after-free. I guess we'll find out when Zig has more widespread use.