Is the grass greener on the other side? Maybe.

I went to play with a real game engine.

I tried Bevy, which is written in Rust and has a thriving community around it. The engine is essentially a combination of an ECS and a rendering engine, the two parts that even in my C++ version I didn’t write myself (raylib for rendering and entt for ECS).

With the kind help of an LLM that explained and guided me step by step (thanks Gemini), and with the help of the avian plugin (a physics engine), I reached a result in a few hours that is close to what took me weeks, sweat, and tears to achieve working with raylib and C++.

Am I tempted to switch to a game engine? Not yet. I really enjoy writing the physics, the rules, and the conditions, and at some point, if I decide to abandon C++ in favor of Rust (is it time?!), then I’ll consider moving to a game engine, even though there are similar libraries to raylib for Rust, and even a version of raylib itself for Rust.

Working with C++ demands discipline from me (and yes, frustrations too), and it seems to me that after C++, the transition to Rust will be easier.

So for now, I’ll maintain a side project in Rust whose sole purpose is learning, so that when the day comes, the transition will be smooth.