4 ms·
Cart explicitly rules out using scripting language and said writing games in the same language as the engine was one of the motivation for him to start a new en
by littlestymaar 6y ago
Cart explicitly rules out using scripting language and said writing games in the same language as the engine was one of the motivation for him to start a new engine.
> Turtles All The Way Down: Ideally the engine is written in the same language that games are. Being able to run an IDE "go to definition" command on a symbol in your game and hop directly into the engine source is an extremely powerful concept. You also don't need to worry about heavy language translation layers or lossy abstractions. If an engine's community builds games in the same language as the engine, they are more likely (and able) to contribute back to the engine.
https://bevyengine.org/news/introducing-bevy/ https://bevyengine.org/news/introducing-bevy/
- suby 6y agoI'm thankful this is his attitude. I think part of the appeal of Bevy is that it is built in Rust, and you are meant to use Rust in building your project. I think it pushes the design to make working in Rust as optimal as possible.
- giancarlostoro 6y agoI could see a Rust-like scripting language being adopted at some point, all it takes is someone building a proof of concept and before you know it, it winds up in the codebase because it's so polished. Which is another thing I love about Bevy, people are allowed to write their own projects and if they're good the Bevy team will take them into consideration (or that's the vibe I got being on the Discord) which is what makes Open Source so great. It's too early for them and them maintaining Rust is certainly a total strength at the very least.