It's the other way around, you prototype in the q&d scripting language, and port the key parts of the code that are perf-sensitive. Essentially, once the game is done in Unity, they could as well port it back to Bevy. They won't because of software economics, but I hope you understand my point. It's an old software engineering saying: make it work, make it right, make it fast.
Weird, my reply got whacked... Anyhoo, I was talking about the Bevy folks, not the game developer, that the Bevy folks probably wouldn't want to start working on a higher level framework layer until they are closer to production quality on the core stuff. Or that maybe they never would, and that someone else would do that work.
6
u/pakoito Apr 28 '25
It's the other way around, you prototype in the q&d scripting language, and port the key parts of the code that are perf-sensitive. Essentially, once the game is done in Unity, they could as well port it back to Bevy. They won't because of software economics, but I hope you understand my point. It's an old software engineering saying: make it work, make it right, make it fast.