Reorganizing in Bevy (0.10 Devlog 2)

[@jacques-dev]

Thanks for making this video, it's great to see how others structure and organize their Bevy projects. Regarding Traits (or the lack there of) I've also really been struggling to best figure out how to make use of Rust traits in Bevy projects. From the few discussions I've had on the topic in the bevy discord, it's my understanding that implementing traits on components is bad practice since components are suppose to only represent data, and not behavior, which traits represent. I am curious to hear how others have used traits in their bevy projects. Also very interesting to see the other projects you are working on :)

[@logicprojects]

Yeah I've seen a couple of people try traits with bevy but they never scale like you'd want. They are kinda like interfaces in OO languages which also tend to lead to bad architecture in game dev. Actually my problem might be trying to just have a general attack component all together, each attack might have different data and behavior. Maybe different components for different attacks is the more idiomatic approach.

[@RSchenal]

Greate project structure! Also I just tried llama and it just blew my mind. I actually can run a language model on my laptop on cpu!

[@logicprojects]

Thanks! Also check out the alpaca model (it's out there), it's not great but the potential is crazy

[@CuriousSpy]

Thank you

[@tsalVlog]

the compression lol

[@logicprojects]

I thought it would be bad but it's much worse than I expected lol. I toned down the particle count going forward

[@cchance]

Love your videos just wish you went a tiny bit slower having to constantly pause to understand because it’s not love coding gets super tedious