Casey Muratori – The Big OOPs: Anatomy of a Thirty-five-year Mistake – BSC 2025
Better Software Conference · 8 位 HN 用户推荐 · 2025–2026
point. The whole "90s style OOP isn't OOP as it was originally intended" thing is largely a myth. When Kay and other OOP pioneers were describing Smalltalk and OOP to professional developers, they all used 90s Java style "compile-time hierarchy of encapsulation that matches the domain model" OOP to explain it. Smalltalk-80: The Language, a book by some of the original designers of Smalltalk, even
— ndiddy, 2025You might also want to watch Casey's great talk on the history of OOP [link]
— hiker, 2025This is the video that's been going around. It's a bit long and could have been compacted into a 20 minute video, but if you have the time, it's a good overview for people without a computer science background. "Casey Muratori – The Big OOPs: Anatomy of a Thirty-five-year Mistake – BSC 2025" [link]
— OhMeadhbh, 2025Reminds me of this fantastic talk: [link]
— ubercore, 2025I enjoyed the pragmatic historical definition of OOP given in [link] where essential it can be seen as subtype polymorphism
— afiori, 2026That'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: [link]
— Rendello, 2026You might like Casey Muratori's "The Big OOPs" talk about this, if you haven't seen it yet: [link]
— tskj, 2026Somewhat related, I’ve been digesting this long but fascinating talk about the even earlier history of OOP, going all the way back to the 1950s. It’s from the perspective of someone who questions some early decisions about what OOP would become. Implementation inheritance, of course, which iirc is something Kay calls out as more accidental than principled language design decision in this paper. Bu
— bunderbunder, 2026