Bevy game engine

“It takes substantially more software infrastructure to make a game engine than just the renderer.”

“The 0.2 version number would typically imply that breaking changes are to be expected and that it’s not ready for commercial projects”

“Overall, it's been a pleasure, and at the time of the 0.14->0.15 upgrade my codebase was small enough that it was done in an hour or so.”

“The breaking Rendering changes have always been the big challenge”

“I have a feeling that Bevy's design played a role in shaping the game and the ease of adding new features”

“They have been introducing breaking changes left and right”

“yes it's very well designed, and because if it's modularity it's well positioned both to support an editor”

“The Bevy team are doing amazing work and it's great to see it being worked on all the time.”

“the performance benefits for something like Bevy only apply to a handful of games that really need it”

“For Bevy to catch up on the indie game scene it needs an editor plus a scripting language”

“The one other downfall of this might be the fact that the compile times make iteration difficult.”

“it's also super hard to do anything procedural like UI animation”

“Bevy was a really nice breath of fresh air when I dipped my toes back into hobby game dev”

“I'm currently building a game with it right now and having a blast.”

“I haven't noticed any performance issues for the things I'm doing.”

“the ECS architecture seems to make it easy for them to reason about how things work”

“Bevu/Rust just made it easier to brute force that scaling, since they have smaller footprints”

“Naturally on such a beefy machine it will fly given how fast Bevy gets compiled.”

“Rust libraries like bevy provide the training wheels to a half decent dev”

“If you want to get inspired by good component DX, try looking at Bevy, the game engine.”

“Bevy which I believe is considered an engine but is code-centered”

“Bevy is a great engine for LLM-based games because it's 100% code.”

“I've been using Bevy myself and I think its only good right now for a niche of experienced enthusiastic hobbyist game devs.”

“You can choose how much of the engine you use and just not import the parts you don't want.”

“has no reason to bloat binaries to be 50MB for an empty program that does nothing”

“Bevy is far easier to test than most game engines because it's”

“The way Bevy's internal state is so easily saved and loaded is convenient for this.”

“About compilation time concerns, it doesn't seem to be a problem with Bevy”

“People say binaries start at 50 MB for a hello world program and 700 MB for the debug binaries.”

“Bevy gives you a very nice ECS to model your app but compilation can be slower than hand crafted code”

“even medium-scale game engines like Bevy take a bunch of time and space to compile”

“bevy seems promising for making performant games without the overhead of using one of the big engines”

“Bevy releases have a lot of breaking changes, and so do many of the 3rd party plugins.”

“It's a cool engine, but I imagine a manufacturer would like to have long-term support with 15-year timelines.”

“I don't think anyone's seriously using Bevy's 3D renderer, only the ECS.”

“In some areas it is quite advanced (rendering) and in others it is lacking / underdeveloped (editors / tooling).”

“This renderer can embed Bevy, a game engine also written in Rust”

“So basically well known and very good Open Source”

“My hope is that something more versatile like Bevy becomes common”

“It has been a pleasure learning and practicing Rust with Bevy.”