shipyard VS scheduler-test

With game matching the binary name used in Cargo.toml, above. The code we use is provided as an example of using the Shipyard Rust ECS. Paste the main.rs square_eater code from the repo into src/bin/main.rs in your project.

I also initially followed the amazing bracket-lib tutorial, but was not satisfied with specs. Tried legion, but it seems kind of abandonned too. I choose to use shipyard in my project and I am pretty satisfied with it until now. I feel like it's a great compromise between usability and effectiveness, plus there is relatively up-to-date documentation. Maybe can you give it a try ?Shipyard

Shipyard (Rust)

It's not that it's incompatible, it's that when the ECS is the primary tool for organization, a DOM tree (or scenegraph) is merely one way of iterating over the entities - not the way.

This provides tons of benefits, so for example you can also decide to iterate over the entites by shader program and gain significant speedups for graphics processing, or maintain components that roughly sort them by their position in world space for physics and culling or lighting, etc.

To add to the sibling comment, there's another wonderful Rust ECS called shipyard[0] and I helped write a scenegraph for it (which I really need to update, one of these days)[1]

[0] https://github.com/leudz/shipyard

Just as a final thing here, are, a, bunch, of, links for shipyard's tuple impls to show how its not an uncommon thing to need to do when writing an ECS :)

this is the test you are referring to: https://github.com/drcmda/scheduler-test it tested against severe stress. the cubes had artifical runtime delay, which would clog the main thread. the github repo now contains a vanilla test that you can run, it will block your cpu for 1-2 seconds. this is repeated every 2 seconds. a vanilla app trying to get through this will consequently go to its knees, but react can schedule it away.

this btw, as absurd as it may seem to you, is a react feature. the upcoming react 18 release is pretty much based on it.

this is complete bs though, he merely removed the stress from the stress-test, the very thing it's testing against. the updated test is here: https://github.com/drcmda/scheduler-test it includes the stress test (500 instances of text geometry), re-created every 2 sec. simply creating them takes 1-2 seconds. svelte, like everything else is going to choke on this. react on the other hand can balance load.