shipyard VS react-three-fiber

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 perfect then. a large part of the threejs userbase is using https://github.com/pmndrs/react-three-fiber (roughly 1/4, and growing) and this is also where you find lots of job opportunities. fiber has a vast eco system, but if you can pair this with your knowledge of shaders you'll find a job tomorrow if you wanted.

there's 3d with threeJS you could play around with that and hooking it into react with react-three-fiber.

Have you looked at this: https://github.com/pmndrs/react-three-fiber

Only instance in recent memory where I was able to get something working with Expo but not the CLI was when trying to integrate react-three-fiber, but even that may be resolved now.

this will put you at a massive advantage: https://github.com/pmndrs/react-three-fiber it's a renderer, just like react-dom, it won't change what threejs is or how it functions.

there's a whole eco system around three in react and next. it starts with react-three-fiber, drei has tons of helpers, and then there's three-next for when you need 100% lighthouse, persisting canvas across routes etc.

I picked the stack I did to expand upon my skill set. In particular, I wanted to brush up on react-three-fiber, react-spring & drei.

I think the easiest for you would be to get into this through web development try this https://github.com/pmndrs/react-three-fiber coupled with this https://github.com/pmndrs/react-xr But don't expect super beautiful graphic from this, it's abstraction over three.js library which is abstraction over webgl standard which implements OpenGL ES 2.0 which is 7 years old graphics standard targeted to mobile devices with not much power. Or you can experiment with unity (unity XR) or unreal engine which are harder to learn but produce better graphics.

On the technical side, the ability to have pluggable renderers has been very useful for us. We never would have considered 3D without react-three-fiber. Building cli applications with react-ink is pretty cool.

Then, we need to install the dependencies that we will use in this project. We will use Three.js library, @react-three/fiber and @react-three/drei.