Re:Data-oriented design or why you might shoot yourself in t...
by beaconstudios on Monday June 28, 2021 @12:43PM
(#27664172)
And ECS is fundamentally a trait system!
[ Parent
| on HN ]
Re:Data-oriented design or why you might shoot yourself in t...
by dkersten on Monday June 28, 2021 @01:18PM
(#27664619)
I know all the terms are overloaded nowadays so everything’s kinda unclear but I always wished that ECS components had been called traits, because adding a component to an entity gives it some a trait like “this thing has a position in the world” or “this thing can be drawn” (and perhaps have systems named “behaviors”, because systems add behavior to entities based on the traits/components that they have)
Years ago, when ECS was just starting to be talked about (after Adam Matrins blog posts), I wrote a toy ECS where I used that naming convention. Nowadays I stick to the mainstream terminology since that’s what other people know.
Re:Data-oriented design or why you might shoot yourself in t...
by pjmlp on Monday June 28, 2021 @04:41PM
(#27667794)
They have, but there is a certain tendency to ignore CS literature.
"Component Software: Beyond Object-Oriented Programming"
https://www.amazon.com/Component-Software-Beyond-Object-Orie...
1st edition, 1998
Re:Data-oriented design or why you might shoot yourself in t...
by beaconstudios on Monday June 28, 2021 @02:17PM
(#27665503)
Yeah I've commented before that "entity component system" is roughly synonymous with "thing piece thing" or something like that - it's a really bad name because it's so ambiguous. Anything including the term trait would be 1000x better because at least "trait" means something.