Stride: Entity Component System Epic

[xen2]

Some improvements need to be done to ECS:

• cache localized data
• easier parallelism/jobs
• easier background preloading to avoid stuttering when a new entity is added to scene

[RUSshy]

I suggest this library: https://github.com/Leopotam/ecs

It optimized and works really well

[Kryptos-FR]

@RUSshy Maybe it works well, but integrating it into Xenko would be a pain: you would basically have to redesign everything. Instead we should build on top of what we already have.

[ghost]

I came here from this comment and the related question about Unity ECS in 2018/2019 DOD or DOTS (data oriented design/data oriented tech stack) the goal here is of course to have a way out of unity vendor lock in with xenko. Is it possible to list where we are at thus far.
https://forums.xenko.com/t/is-it-possible-to-incorporate-ecs-pattern-with-xenko-engine/1548/15

For us and many studios the time to pivot is now. xenko is only place I can find mention of brdf besides blender folks. So with rendering and c# support and now open source annoucements, huge potential for studios looked to have a way out to mirror their code changes in way we can port out of unity if we need to for licensing etc.

I do see that Svelto.ECS a few places. I saw it on godot i think. Not sure if he is just good at posting on forums or if it is actually good. Just wanted to document the consideration and ask for any list of what we might be able to do to port Unity to xenko using the DOTS path, so no vendor lock in but similar quality.

[Shpendicus]

Hey ppl is anything happened in this regard to Stride since then? WOuld really love ot hear about this! :)