this post was submitted on 29 Apr 2025
83 points (92.8% liked)

Programming

19927 readers
176 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 7 points 2 days ago* (last edited 2 days ago)

In our experience at $DAYJOB, Rust is actually not too bad, when it is one of the first languages that someone learns. It's definitely a lot more troubling for experienced devs who have certain patterns in mind, which they can't replicate in Rust. They tend to struggle a lot, whereas our students generally pick up and work with Rust like it's any other language.

But Rust + Bevy is probably more confusing. I actually started my journey into Rust with a (much less mature) game engine, too, which also used an ECS. And well, the ECS kind of bypasses Rust's memory management, which I didn't understand until much later. I didn't really learn Rust's memory management model until 5 months in, even though I was partially using it...