#Posting My Bevy Notes So Other Beginners Can Read And Comment
27 messages · Page 1 of 1 (latest)
ty
@tired quartz
composition is still really important in OOP, but in bevy/rust you want to separate as much as possible because of mutable borrows
forgetting to add events and resources is also a thing
enums can also be components, and using them actually feels really close to interfaces
methods should also feel familiar
if you filter query by marker component, it basically becomes a class but without the downsides
Alright, fixing
I'm not sure what you mean with the note "methods should also feel familiar"
also you can comment inside the file itself, would make it clearer where and what should be changed
also I'm not sure how to continue that line
I read the book and know what methods are
OOP classes have data and methods that can easily access that data even if it's private
data is a component, and you can add a method to them
true
they're actually even better than interfaces since in rust they can hold different data
I know
(should I also share my Rust notes haha)
traits are closer to interfaces/polymorphism but from what i understand it's not quite there yet
are you coming from unity?
I've been through Unity and Godot
While I am a fan of C# I'm not a fan of Python
right
I've been learning Rust for the past month, so I'm familiar with the common thinking patterns
a book for unity/godot refugees might be really useful
true
so it's worth combining rust and bevy into one place that teaches everything with a smooth learning curve
I might do that in the future, it's just that I've been learning Bevy specifically for about two days now
So I don't have a clear picture yet
So far many things I've learned that are very relevant to Rust in general seem useless here
the main struggle for me is still the borrow checker and not being able to cleanly split up the functions