The case for Lazybox ECS about specs HOT 2 CLOSED

@kvark I'm not sure what exactly this issue is useful for. Are there any points we should address or is it a just comparison?

Also we have the concept of Accessors that statically ensures to the user and the library that the entity is alive and the reference valid.

We don't have that, but I'm not sure about the limitations it brings

We have Groups that are like Aspects that represents a set of entity that Systems can iterate on instead of calculating it each processing steps although it introduces its own caveat.

Seems like we have that

Our System Scheduler is based on what systems need to read and write instead of associating a priority to each system, but I suppose we could implement this on top of specs.

Highly flexible on our side:

• dependencies
• aspects
• barriers
• or manual RunNow / user-built scheduler

At last, we had a lot of trouble to handle serialization and our new ecs is (in theory) designed to ease that.

Serialization could be easier.

from specs.

Moved to wiki.

from specs.