A Thought Experiment: Using the ECS Pattern Outside of Game Engines

Re:A Thought Experiment: Using the ECS Pattern Outside of Ga... by skybrian on Saturday December 28, 2019 @11:31AM (#21899768)

Yes, ECS is usually about runtime changes in behavior. It also uses IDs rather than hard references, like in a database. Deleting an object makes references to it invalid, rather than references keeping objects alive like in a functional or object-oriented object graph.

[ Parent | on HN ]

Re:A Thought Experiment: Using the ECS Pattern Outside of Ga... by spankalee on Saturday December 28, 2019 @02:39PM (#21901188)

But the complaints about OOP in the article are all about the difficulty in modeling orthogonal traits in a single-inheritance hierarchy. That is definitely addressed with mixins.

Nothing in the "Inheritance isn't Always the Best Tool for the Job" section talks about runtime changes in behavior.

[ Parent | on HN ]

Re:A Thought Experiment: Using the ECS Pattern Outside of Ga... by skybrian on Saturday December 28, 2019 @09:25PM (#21903465)

It does touch on it towards the end:

> Most object-oriented languages are designed so that an object's underlying type will be the same for its entire lifetime. This makes things interesting when users want to scale a Circle without maintaining aspect ratio.

[ Parent | on HN ]