Thanks. I think Ecspanse and ECSx try to solve the same “problem” but in different ways. I even mentioned ECSx as an alternative to Ecspanse in my Medium article.
Still, to try to answer your question, I think ECSx is more straightforward to get started with. You have generators and every component holds a single value. You can then query the individual components by their entity ID or as a list. But I think their guides section explains it better than I could.
On the other hand, Ecspanse has a bit more complicated approach, but I would say also offers more flexibility as the game becomes more complex. I would mention just a few of them:
- complex queries across multiple components, entities, and relationships
- out-of-the-box bidirectional entities relationships to make it easy to work with trees of entities, but especially with collections
- component templates and tags - to handle component collections and polymorphism.
You can find some more details and examples in the Medium article.
