Theres 2 major aspects of ECS that are good for gamedev. They can be implemented together or separate, and games have been using both of these since the 90s only without all the new fangled terminology.
Your ECS is a great description of a decent way to lay out fast, cache aware systems.
For gameplay I prefer the other type of component systems. This one is generally seen as using GetComponent(); then operating on it or doing something else if it doesnt exist. Unity uses it ok, but the best example of it via a talk by Brian Bucklew the primary developer behind Caves of Qud.
I feel LISP/Scheme style languages would be great at building nice DSLs for handing both types, whether individually or together. Ive never really put an ideas to paper here though.
Theres 2 major aspects of ECS that are good for gamedev. They can be implemented together or separate, and games have been using both of these since the 90s only without all the new fangled terminology.
Your ECS is a great description of a decent way to lay out fast, cache aware systems.
For gameplay I prefer the other type of component systems. This one is generally seen as using GetComponent(); then operating on it or doing something else if it doesnt exist. Unity uses it ok, but the best example of it via a talk by Brian Bucklew the primary developer behind Caves of Qud.
I feel LISP/Scheme style languages would be great at building nice DSLs for handing both types, whether individually or together. Ive never really put an ideas to paper here though.