Bevy, the future powerhouse game engine that will power many games.Today I break down the core philosophy of this game engine, and outline why the engines co...
I love Bevy, I made a lot of little things that I loved to program. I’ve never developed such deep love with a programing paradigm. But recently I moved to Godot and actually started finishing projects. When I was using Bevy, I kept making tools, loaders, engines, formats just to make it possible to load into what I envisioned but never finished anything. In about 45 minutes I made multiplayer pong in Godot with different maps and game modes, lobby screen and main menu, what took me a couple of weeks in Bevy with UDP packet design and several iterations.
When I program in Rust, I go for perfection. When I use Godot, I actually finish stuff. Only realize this a bit late now.
For reference, I write custom applications for Shopify, including cart extensions in Rust using Shopify Functions and maintain a block-based blog manager that integrates with Shopify in PHP as well as several micro services in Node.js for other integrations.
If someone could tell me where it went wrong, please do, I love Bevy but I can’t use it effectively.
Bevy is too new; the ecosystem needs to mature big time.
If you’re building anything with Bevy you should do so with the mind set of upstreaming as much as you can to help it grow.
It’s entirely possible to finish a project in Bevy but you’d have to plan as much as you can before hand and focus purely on that, avoiding scope creep as much as possible.
Godot is essentially a finished product, but Bevy still has a long way to go.
I think it’s a common issue with rust in general that a lot of its big impressive libraries/frameworks are still in 0.x with variable degrees of documentation and ease of use. Axum, Rocket, Dioxus, Leptos, Bevy, Servo, the list goes on. A lot of cool things are being built in Rust but very few of them are mature yet.
I love Bevy, I made a lot of little things that I loved to program. I’ve never developed such deep love with a programing paradigm. But recently I moved to Godot and actually started finishing projects. When I was using Bevy, I kept making tools, loaders, engines, formats just to make it possible to load into what I envisioned but never finished anything. In about 45 minutes I made multiplayer pong in Godot with different maps and game modes, lobby screen and main menu, what took me a couple of weeks in Bevy with UDP packet design and several iterations.
When I program in Rust, I go for perfection. When I use Godot, I actually finish stuff. Only realize this a bit late now.
For reference, I write custom applications for Shopify, including cart extensions in Rust using Shopify Functions and maintain a block-based blog manager that integrates with Shopify in PHP as well as several micro services in Node.js for other integrations.
If someone could tell me where it went wrong, please do, I love Bevy but I can’t use it effectively.
Bevy is too new; the ecosystem needs to mature big time.
If you’re building anything with Bevy you should do so with the mind set of upstreaming as much as you can to help it grow.
It’s entirely possible to finish a project in Bevy but you’d have to plan as much as you can before hand and focus purely on that, avoiding scope creep as much as possible.
Godot is essentially a finished product, but Bevy still has a long way to go.
^ Couldn’t possibly agree with this anymore!
I think it’s a common issue with rust in general that a lot of its big impressive libraries/frameworks are still in 0.x with variable degrees of documentation and ease of use. Axum, Rocket, Dioxus, Leptos, Bevy, Servo, the list goes on. A lot of cool things are being built in Rust but very few of them are mature yet.