BObobajeff·Oct 21, 2026
That sounds very simple. And yet it's apparently not:
https://github.com/bevyengine/bevy/issues/26055
In Bevy 0.20bevyengine
bevy
Rust2020–2026
bevyengine / bevy
bevy
A refreshingly simple data-driven game engine built in Rust
55Distinct people
82Mentions
1Explicit recommenders
49.7KGitHub stars
What to know before exploring
What it is
A refreshingly simple data-driven game engine built in Rust
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
We don't have a "complete" official example of those things, although the "game menu" example has some of that: https://github.com/bevyengine/bevy/blob/main/examples/games/...…
_cart used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- emilk/egui · linked in 2 of the same discussions
- gfx-rs/wgpu · linked in 2 of the same discussions
- meomix/symbiants · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 2:04:58 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year82 dated mentions
Observed mentions: 2020-08-11 18:08:23 UTC to 2026-10-21 14:04:51 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 8 | 2 | 6 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 12 | 1 | 11 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 6 | 0 | 6 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 22 | 1 | 21 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 18 | 0 | 18 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 12 | 3 | 9 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 4 | 1 | 3 |
What Hacker News says
4 sourcesI was curious how the design was arrived at and found some of the trade-offs discussed in this issue[0]. I personally liked the idea of using a combination of semicolons and commas to separate entities and components; but oh well, I guess we'll get used to the double-dash.
[0]: https://github.com/bevyengine/bevy/issues/25616
In Bevy 0.20Bevy – A refreshingly simple data-driven game engine built in Rust
7 points · Open discussionWell, if you confronted me with an individual case of course I would feel empathy. That wouldn't change that I think they have incorrect ideas about open source, but I also wouldn't judge them either.
My point is more that people should try to have more realistic views about open source. People aren't obligated to credit your MIT licensed code (beyond the licence file) and you should be clear on that when you chose that licence. Heck, I've seen OSS maintainers outraged because someone forked their code, despite prominently crediting the source [0]. Some people consider that "bad form", in the same way people might consider monetising something previously open source to be "bad form". I think in both cases, people should just choose more appropriate licences. Can't have your cake and eat it too.
I think Hecrj put it well here:
> 'Me giving
Read the rest
away more "free gifts" cannot ever be considered "competing" with someone else that is also giving away "free gifts". The only way for someone to conclude that is if the original gifts are not truly "free", but come with some "hidden" expectations attached to them.'
If you believe that there are expectations attached to your code, you should choose a licence congruent to those expectations. Trying to enforce that through culture is probably a bad idea and will lead to strife.
> Ultimately, I am optimistic that we will continue to establish better and better ways to create sustainable projects with maintainers that are compensated for their efforts.
Yes, I hope so too.
0: https://github.com/bevyengine/bevy/issues/19296#issuecomment...