Bevy Isn't Ready for Large-Scale Game Projects Yet – A Novice's Experience

especially in Rust, making new “classes” can be tremendously time consuming, reusing Series with a different dtype might save bevy users from needing to impl X for Y a billion different times to make a new struct Y. Series already has implementations for whatever is needed.

It’s too bad Polars separates Row from Series so hard in the type system, because this is the true 100x gain of Pandas: evading the OOP paradigm with thing_ser and things_df instead of class Thing and Tuple[Thing, …]

I.E. instead of forcing Bevy devs to pass around these heinous Query, Query, Query signatures and remember the order, maybe a “creatures_df” with appropriate columns would be more fun to work with because it’s a bit higher level but still performant (and possibly less code to maintain by pushing work onto Polars)

More focus on polars row feature imho is needed for the rust community to thrive, it’s a backwater in that workspace which could become a saving grace

Edit: also, an easy compilation gain is to… # Parallelize Rustc: https://blog.rust-lang.org/2023/11/09/parallel-rustc.html

Makefile:

RUSTFLAGS_VALUES = "-Z threads=8"

test: test-stable

.PHONY: test-nightly test-nightly: RUSTFLAGS=$(RUSTFLAGS_VALUES) cargo +nightly nextest run

.PHONY: test-docs test-docs: RUSTFLAGS=$(RUSTFLAGS_VALUES) cargo +nightly test --doc

.PHONY: test-stable test-stable: cargo test

cfg: RUSTFLAGS=$(RUSTFLAGS_VALUES) cargo +nightly -Z unstable-options rustc --print cfg

# Run tests and benchmarks every time a file changes

watch-nightly: RUSTFLAGS=$(RUSTFLAGS_VALUES) cargo +nightly watch -x "nextest run" -x "test --doc"