Live data from Hacker News

Bevy 0.14 – Data driven game engine

bevyengine.org

21–30 of 50 posts

Re: Bevy 0.14 – Data driven game engine

#21
post #7
post #3

Earlier quoted context omitted.

Noteworthy: this was our first release that used our new Release Candidate (RC) process and automation to facilitate collaboration on the release blog post. Both of which were a great success! The quality bar of the release has been raised significantly: expect fewer bugs and faster 3rd party plugin updates!

Any information you can provide on the automation for the release posting? This seems to be the hardest part for me.

Our new release notes process is outlined here: https://github.com/bevyengine/bevy-website/issues/1163

Re: Bevy 0.14 – Data driven game engine

#22
post #7
post #3

Earlier quoted context omitted.

Noteworthy: this was our first release that used our new Release Candidate (RC) process and automation to facilitate collaboration on the release blog post. Both of which were a great success! The quality bar of the release has been raised significantly: expect fewer bugs and faster 3rd party plugin updates!

Any information you can provide on the automation for the release posting? This seems to be the hardest part for me.

There is a Rust tool named `generate-release` within the website repository[0]. It handles interacting with the Github API to get a list of significant changes, breaking changes, and contributors. (The main Bevy repository has pull request labels for all of these, so this is pretty easy.)

[0]: https://github.com/bevyengine/bevy-website

Re: Bevy 0.14 – Data driven game engine

#23

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…

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

Re: Bevy 0.14 – Data driven game engine

#24

Earlier quoted context omitted.

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.

These are different articles being posted, not dupes.

Thanks for editing out the line where you told me to go get my brain checked.

Re: Bevy 0.14 – Data driven game engine

#25
This release has Observer and Hooks which in my opinion really elevate the ability to express complex, reusable structures in the ECS.

For example, one of the well-known challenges in the paradigm is working with hierarchies or graphs - observers are a powerful tool for communicating between specific entities, and should make this a lot easier to express.

Hooks offer the ability to enforce cross-component consistency in a way that wasn’t previously available.

Re: Bevy 0.14 – Data driven game engine

#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 Observers and Hooks are really nice and will allow me to more cleanly implement a feature that I've been needing (Optional Components).

Re: Bevy 0.14 – Data driven game engine

#28

Earlier quoted context omitted.

These are different articles being posted, not dupes.

Thanks for editing out the line where you told me to go get my brain checked.

Not sure what you’re talking about. Perhaps you saw a different comment.

Re: Bevy 0.14 – Data driven game engine

#30

Earlier quoted context omitted.

> to qualify as a new Show HN there needs to be some major new development, not just a new feature One could argue a major version qualifies. Apart from the genuine dupe 3 months ago all of these are separate stories. dang's comment also specifically covers "show hn" posts which this is not. Some clarification from dang would be helpful though.

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.
Post reply on HN