Casey Muratori | Smart-Pointers, RAII, ZII? Becoming an N+2 programmer

Why HN readers recommended it

HN commenters in memory management and language design threads cite it as the best explanation of group lifetimes versus per-object ownership.

This is a summary from the source dataset, not an endorsement by Hacker News or the video creator.

Video & recommendation details

Creator / channel

xDahl

Topic

memory management paradigms

Format

talk

Level

advanced

HN recommenders in dataset

6

HN mentions in dataset

9

Recommendation years in dataset

2024–2026

These counts and years describe the included Hacker News records; they are not YouTube views or the video’s publication date.

From the original HN conversations

Excerpts from the recorded comments. Follow each source for the full comment and surrounding discussion.

• C and C++ are very different. I think Casey Muratori hits the nail on the head here: [VIDEO] In short, RAII and smart pointers and borrow checker are all signs of "individual element thinking" and that way lies madness. You smear out lifetime and ownership …

• Unfortunately I don't think you've understand what I was I trying to say. Rust was designed from day-0 around explicit individual-value based initialization. Odin from day-0 was not designed around this (explicitly). This ever so minor choice might not seem like a big thing to …

• Above poster is talking about thinking in terms of grouped lifetimes and bulk allocations/deallocations, which is better for performance, and makes Rust borrow checking and other RAII style features completely pointless as they don't add any safety benefits. I used to think like you until …