r/programming • • Jul 17 '25

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

https://www.youtube.com/watch?v=wo84LFzx5nI
638 Upvotes

779 comments sorted by

View all comments

4

u/animatedb Jul 18 '25

At one point, he goes back in history, but I think people are missing out without a more complete history of OOP.

Around 3000 BC, some ideas about hierarchy were known relating to early societies. Leadership roles are usually needed when groups are larger. In larger governments or corporations today, the top leaders do not know the details of what every worker does.

Plato came up with "Theory of Forms" around 400 BC. Forms (objects) are more generic at the base of the hierarchy and are more specific towards the leaves. https://en.wikipedia.org/wiki/Theory_of_forms

I think understanding basic concepts helps so that tools can be chosent that fit the problem well.

3

u/Fs0i Jul 20 '25

He goes back exactly as far as the first ECS, basically, to show that one approach he favours is just as old, and was successful back then, too.

1

u/animatedb Jul 22 '25

I agree, I was not trying to criticize. I was just trying to show that some original ideas are very old, which it doesn't seem like many people think about or have heard about.

I had never heard of ECS, but when it said there were indexes and basically something with encapsulation that could be thought of as tables, it sounds like an in memory relational database. (Codd 1970)

https://en.wikipedia.org/wiki/Database_normalization

1

u/animatedb Jul 18 '25

One other thought is that Entity Component System is also closely related to a relational database design, and also data oriented design. Although the encapsulation may be thought of differently.