Live data from Hacker News

Bevy 0.14 – Data driven game engine

bevyengine.org

31–40 of 50 posts

Re: Bevy 0.14 – Data driven game engine

#31
post #2

Bevy's creator and project lead here. Feel free to ask me anything!

Probably been answered already (feel free to point me there) but how does Bevy compare with Godot (other than one might prefer Rust)? What type of game/situations would Bevy be much more performant where it matters?

Re: Bevy 0.14 – Data driven game engine

#32
post #30

Earlier quoted context omitted.

Your quote omits the portion where Dan explicitly addressed that case. It needs to be one year since it received “significant attention,” and also major new development. Dan’s post could be worded more clearly, though. (We’re pretty far in the weeds here, but as long as we’re here – for all intents and purposes, this is a show HN.)

It appears that Show HN has special algorithmic handling, which is why you would expect stricter rules.

Good point - I just linked to the first relevant explanation. pvg linked to a much longer explanation that isn’t specific to, or about, Show HN: https://news.ycombinator.com/item?id=23071428

Re: Bevy 0.14 – Data driven game engine

#33
post #9

Earlier quoted context omitted.

This is _not_ a repost from our perspective. This is a massive new chunk of features and content (993 pull requests from 256 contributors) including new hot-topic features like Virtual Geometry.

Please reread https://news.ycombinator.com/item?id=9775868 . It says one year since it received significant attention, not one year except when a massive chunk of features and content is added. Dan explicitly addresses that case (“but that only applies after the "significant attention" test has been passed”).

[deleted]

Re: Bevy 0.14 – Data driven game engine

#34

Earlier quoted context omitted.

What a bad faith comment. How is a new version announcement a dupe? If you don’t care then you don’t have to comment.

Don’t rely on my assessment, go read https://news.ycombinator.com/item?id=9775868 . If you disagree, don’t tell me, suggest an improvement to Dan.

> don’t tell me

You are the one initiative here.

Re: Bevy 0.14 – Data driven game engine

#35
post #26

The states improvements are definitely nice, and I did run into the whole "Unable to transition into current state" issue, as I was using it for a respawn. I ended up just making a "Respawn" state, and then quickly switch out of it to reset back to the original. With this being in it definitely would make things a lot cleaner in some ways, as I can at least get the whole "Re-enter State" a bit easier. Also the Observ…

You can also check out my 3rd-party crate `pyri_state` for easier state refreshing (https://github.com/benfrankel/pyri_state/blob/main/examples/...) + other features like state pattern-matching. Just released v0.2.0 for bevy 0.14 :)

Re: Bevy 0.14 – Data driven game engine

#36
post #2

Bevy's creator and project lead here. Feel free to ask me anything!

Probably been answered already (feel free to point me there) but how does Bevy compare with Godot (other than one might prefer Rust)? What type of game/situations would Bevy be much more performant where it matters?

Bevy makes it much easier to write reasonably fast, easily maintained, refactorable code. It's great for situations where you have a lot of complex logic, want to do something particularly weird, or require a lot of non-rendering performance (Unreal still crushes us on rendering performance due to several decades and billions of dollars of investment).

Factory builder and simulation games are the classic example of "when should you use Bevy". You should absolutely pick Godot right now for games that are more content-focused that need a lot of level design: puzzle games, platformers, walking simulators...

Re: Bevy 0.14 – Data driven game engine

#37
post #6
post #2

Bevy's creator and project lead here. Feel free to ask me anything!

I know the latest UI update/plan is not released yet, but do you feel like you’ve discovered the way forward in that area? Or are there still lots of unknowns?

Outside of the core reactivity and scenes work, I'm really excited about the improvements in both text rendering and picking. I think both of those will make a huge difference in terms of usability and correctness.

Once those are a bit more stable, I'd like to target a focus system for UI, to enable good keyboard and gamepad menu navigation and to hook up to screen readers.

Re: Bevy 0.14 – Data driven game engine

#38

Effectively a dupe - this just got attention 3 months ago ( https://news.ycombinator.com/item?id=39672947 , https://news.ycombinator.com/item?id=39677009 ) and 8 months ago ( https://news.ycombinator.com/item?id=38144417 ). Once a year has been suggested as the typical maximum frequency: https://news.ycombinator.com/item?id=9775868 . Consider reposting in 2025. Also, coordinating comments and upvotes won’t do you any…

> Effectively a dupe - this just got attention 3 months ago

Wait until you realize Rust new version makes it to the front page every 6 weeks… (It's a bit less true these days because Rust release are much more boring than they used to, but it was definitely the case just a couple years back)

Re: Bevy 0.14 – Data driven game engine

#39

Earlier quoted context omitted.

What a bad faith comment. How is a new version announcement a dupe? If you don’t care then you don’t have to comment.

Don’t rely on my assessment, go read https://news.ycombinator.com/item?id=9775868 . If you disagree, don’t tell me, suggest an improvement to Dan.

You've pointing a a “Show HN”, it obviously doesn't apply to other kinds of posts (or are you gonna limit OpenAI's announcement links to once a year too ? ;)

Re: Bevy 0.14 – Data driven game engine

#40
post #23

Earlier quoted context omitted.

What a bad faith comment. How is a new version announcement a dupe? If you don’t care then you don’t have to comment.

How is a new version announcement a dupe? Lengthy explainer here https://news.ycombinator.com/item?id=23071428

According to this, the submission is fine: it's a major version announcement, unlike the examples given in the post, with significant changes, which rule out the “the diff between Foo 1.3.3 and the last time Foo came out is not enough to support an interestingly different discussion”
Post reply on HN