@modev
@modevstudio.itch.io
I write code, gamedev.
https://sr.ht/~modevstudio
https://sr.ht/~modevstudio
Nice view. Nature save us from burnout sometimes...
January 18, 2026 at 7:25 PM
Nice view. Nature save us from burnout sometimes...
Because static lifetime entities lives wile the world exists there are no deleting mechanism for them in its blocks, and components are simply inserted to the next free row or new block will be inserted if current one is full.
January 13, 2026 at 12:22 PM
Because static lifetime entities lives wile the world exists there are no deleting mechanism for them in its blocks, and components are simply inserted to the next free row or new block will be inserted if current one is full.
For quick lifetime, entities and components are previously stored in the buffers and passed by reference to ECS.
When buffers are full they will be flushed to newly created block on the heap. If entities not outlive the size of quick lifetime block, access to them will be as fast as stack memory.
When buffers are full they will be flushed to newly created block on the heap. If entities not outlive the size of quick lifetime block, access to them will be as fast as stack memory.
January 13, 2026 at 12:22 PM
For quick lifetime, entities and components are previously stored in the buffers and passed by reference to ECS.
When buffers are full they will be flushed to newly created block on the heap. If entities not outlive the size of quick lifetime block, access to them will be as fast as stack memory.
When buffers are full they will be flushed to newly created block on the heap. If entities not outlive the size of quick lifetime block, access to them will be as fast as stack memory.