Hacker News Reader

Comment by avolcano | Hacker News Reader

Something delightful about this update: it has a lot of new features, some very early, but all by different authors. Seems like such a community effort compared to most early-stage projects, which usually are driven by one author in relative secret until they are closer to some dream "1.0".

View on HN

The BDFL of the project, cart, shows a lot of emotional intelligence in this Amethyst community post about Bevy: https://community.amethyst.rs/t/bevy-engine-addressing-the-e...

I’m not surprised they have the ability to muster a community fairly quickly. Probably shared a lot of contributors with the Amethyst project.

Links on that page don’t quite work like you’d expect — your link goes to the post Carter is responding to (which is worth reading too). This one goes straight to his post.

https://community.amethyst.rs/t/bevy-engine-addressing-the-e...

I specifically posted the entire thread for context, but thanks for the link to cart’s comment.

Last this project was posted I joined the Discord and it seems to be a friendly space and a LOT of people joined and shared ideas. I think given a year or two this project (rightfully so!) will ressemble Godot (its an inspiration for Bevy). I am curious if they will adopt a scripting language similar to how Godot has GDScript. I think Godot was in the right in implementing their own language that fits their engine best.

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/

I'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.

I 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.

Big props to cart (and of course everyone contributing!) for putting a huge focus on community development after release. It can be challenging to set aside the fun work but it looks like it has paid off so far. The async task system and WASM work are particularly exciting community contributions -- Bevy is much closer to being a viable web-game engine now thanks to those.

Reply on news.ycombinator.com