https://en.wikipedia.org/wiki/Entity_component_system#Characteristics

> This eliminates the ambiguity problems of deep and wide inheritance hierarchies often found in Object Oriented Programming techniques that are difficult to understand, maintain, and extend. Common ECS approaches are highly compatible with, and are often combined with, data-oriented design techniques.

I'm sorry what? Generics and multi-methods #ObjectOriented systems (https://en.wikipedia.org/wiki/Multiple_dispatch) have no such problem.

https://functional.cafe/@awkravchuk/110490845045463704

#CLOS #CommonLisp #Wikipedia

Entity component system - Wikipedia

I wanted to add a note in the talk page about that discrepancy but apparently #wikipedia doesn't like #Tor-using editors, even when logged-in now.

It really just irks me when people conflate #SingleDispatch #ObjectOriented programming with #MultipleDispatch.

They're both #OOP, but they have some pretty drastic differences in how they go about it and that has consequences for the code's maintainability and often performance as well.

@lispi314 “I made up the term ‘object-oriented’, and I can tell you I did not have C++ in mind” — Alan Kay (note that all the shit-ass OOP languages like Java decided that C++ was the best model to imitate)