|
|
|
|
|
by pjmlp
1709 days ago
|
|
I also did not state that book was the canonical ECS model, rather that it was one of the first sources to move into discussing components instead of classes. COM and DirectX aren't distributed object systems, nor Objective-C protocols, for example. Don't confuse COM with DCOM and COM+. Then there are the component models based on traits, mixins, patterns, message passing, type classes,... plenty of variants scattered around SIGPLAN and ECOOP papers. |
|
The book is one of the first sources to move into discussing "components," as in coding against interfaces/protocols/traits/etc.
ECS deals with "components," as in pieces of data composed using a relational model. This has nothing to do with interfaces or protocols whatsoever! It is practically the opposite thing- working directly with raw data, with no abstraction boundary.
You can't just pattern match on the word "component" and expect it to mean the same thing to everyone.