[SeanAnderson]

Yeah, my experience has been similar. On the one hand, it's exciting to have new features every few months. Some of those features very much so addressed pain points in my code and I was excited to adopt them. Other times, changes were introduced which offered new ways of developing, but didn't deprecate old ways nor were they strongly opinionated in which way should be applied in which scenarios.

Overall, I had a lot of fun learning the ECS paradigm, and I found Bevy to make working with Rust easier than learning Rust on its own because it did a good job of hiding lifetimes from me in a lot of situations, but I never got to a point where I felt like I was able to develop ideas quickly.

I'm optimistic about revisiting the code I wrote at some point and seeing how things have improved. It's been maybe a year and a half since I stopped working on a pet project, but I still keep up with all the release notes and have seen lots of things to be excited about. For example, hot reloading is well on its way to being stable and their UI components are becoming much more robust.

https://ant.care/ I built this with Bevy (code here: https://github.com/MeoMix/symbiants/) but have moved on to other projects for the time being.

It's a cute lil sim. It'll crash on you at some point 'cuz there's a race condition when ants come back from the outer-world while hauling food, but it's still kinda fun to watch 'em go.

(Also, while I'm yapping. https://loglog.games/blog/leaving-rust-gamedev/ is very true BUT ALSO people have made successful games using Bevy, or parts of it, e.g. https://store.steampowered.com/app/2198150/Tiny_Glade/)