Hacker News Reader

> Sometimes we might also just choose the bear the cost. For systems with low risk profiles (eg internal software that is never exposed to hostile input) we might decide that debugging the occasional use-after-free is preferable to adding development friction.

Zig vs Rust vs C aside, this cannot be a serious position for a software developer to take in 2021 CE.

View on HN

it's about context.

Suppose you just document "please take this into account" because it's a low-level FFI library, that's being called by a high-level PL, which will make sure that your memory management is sane.

An analogy: "non-threadsafe" code; typically you just tag 'non-threadsafe' and if someone misuses it, it's on them.

Reply on news.ycombinator.com