Casey Muratori – The Big OOPs: Anatomy of a Thirty-five-year Mistake – BSC 2025

Channel:Better Software Conference · Length:2:27:33 · Published:2025-07-17 · Views:939354

Watch on YouTube

Summary

Casey Muratori's two-hour talk tracing the history of object-oriented programming back to the 1960s and examining how its ideas, and later entity component systems, came about. It is followed by a Q&A.

Why HN recommends it

HN commenters recommend it for its source-based history of OOP, though some dispute its account of Alan Kay.

which really is hunting back and back for the cosmogenesis of objects, and covers so much terrain. — HN, 2025

Software architecture & design · Software performance & optimization · Game programming & engines

Subtitles (excerpt)

Please join me in welcoming the one, the only, the irreplaceable Casey Muradori. Okay. Okay. Way too big. Sam Sam made it way too big. I feel like before we start, we should also thank Sam for putting this together. Uh it's been a very long time since I've been really excited to give a talk and uh a lot of that is because the the the speaker list of this talk is is of this conference is absolutely amazing and I just I don't know I'm I'm really excited to be here and I'm excited to give this talk. So I'm just going to jump right into it. So, I would like to talk about something that happened in 1998 at a company called Looking Glass, which normally like back in the day, contemporaneous with this, if I had said Looking Glass, everyone would know who they were because they were incredibly influential game company that did a lot of uh firsts in gaming. Uh, one of their games, Ultimate Underworld, started kind of the 3D revolution in, you know, PC gaming. And they they were incredibly like innovative company at the time. And a lot of people today, I mean, there's people in the audience here who weren't even born then, right? So, a lot of people they might not know who they were, but they were incredibly

On Hacker News

I'd love a deeper dive on how Objects work in NeXTSTEP. From their brochures, they talk about objects being persistent and distributable, that in a workgroup of people everyone can rely on the objects being up to date. I've always been so curious what the broader technical ecosystem looks like here. Presumably there are still processes running on systems. But these processes have lots of objects … — jauntywundrkind, 2025-11
Here is an example of a 2006 rant that qualifies: [LINK] OO conflates many different aspects that are often orthogonal but have been conflated together opportunistically rather than by sound rigor. Clearly most languages allow for functions outside classes. It's clearly the case today especially with FP gaining momentum, but it's also clear back then when Java and the JVM were created. I think sm… — fmjrey, 2025-11
That's one of the things Mike was pushing back on (in the context of C++ / game dev; there's a good example ~20 min in). In case you haven't seen it, Casey Muratori's The Big OOPs: Anatomy of a Thirty-five-year Mistake digs into the different ideas and viewpoints surrounding OOP and how it coalesced into a dogma: [VIDEO] — Rendello, 2026-06
Sounds like you would appreciate this talk: [VIDEO] Personally I use C or something, anything other than C++ really, if I need something more ergonomic or provably correct. Many excuse C++’s design history with “they didn’t know better”, but the oft forgotten history explained in that video shows otherwise. — eska, 2026-05
I enjoyed the pragmatic historical definition of OOP given in [VIDEO] where essential it can be seen as subtype polymorphism — afiori, 2026-02

Related videos