Live data from Hacker News

The Bevy Foundation

bevyengine.org

21–30 of 82 posts

Re: The Bevy Foundation

#21

Earlier quoted context omitted.

Yes. But when I tried the tutorials, the performance issue was an instant turn down. With this, the frame rate immediately went from 13 fps to 60 fps.

The curse of "zero cost abstraction" strikes again :/ A 5x performance difference between debug and release mode isn't uncommon in C++ either and a real problem for game development (plus the slow build times, but those two problems go hand in hand - you can have "high-level abstractions" that build slowly and run fast, or build fast and run slowly). That's why there's so much advice to write C-like C++ and also igno…

Debug mode isn't always needed, though - E.g. C++ with RelWithDebInfo gets you far enough, unless you specifically want to run debugger - I'm one of those who do not use a debugger in their workflow, so a non-issue for me.

Re: The Bevy Foundation

#22

Earlier quoted context omitted.

The curse of "zero cost abstraction" strikes again :/ A 5x performance difference between debug and release mode isn't uncommon in C++ either and a real problem for game development (plus the slow build times, but those two problems go hand in hand - you can have "high-level abstractions" that build slowly and run fast, or build fast and run slowly). That's why there's so much advice to write C-like C++ and also igno…

Debug mode isn't always needed, though - E.g. C++ with RelWithDebInfo gets you far enough, unless you specifically want to run debugger - I'm one of those who do not use a debugger in their workflow, so a non-issue for me.

That's been my fallback solution too in C++ in the past and it kinda works (and Visual Studio has a special option /Zo since quite a while https://learn.microsoft.com/en-us/cpp/build/reference/zo-enh..., not sure though if that's actually used by cmake's "RelWithDebugInfo" config), but there's still downsides even when not using a debugger. Most importantly: if you have a crash/assert handler which logs out a callstack, that callstack may sometimes be quite misleading (depending on how much the optimiser passes have mangled the compiler output relative to the input source code).

Re: The Bevy Foundation

#24
post #17

Earlier quoted context omitted.

This + more is described if you follow the Quickstart, which if it's your first time, is probably the best place to get started quickly :) https://bevyengine.org/learn/quick-start/getting-started/set...

Yes. But when I tried the tutorials, the performance issue was an instant turn down. With this, the frame rate immediately went from 13 fps to 60 fps.

Yeah, I'm guessing that's exactly why that step is like step #3 in the official quickstart tutorial.

Re: The Bevy Foundation

#25

Loved bevy since the reddit post (i think that was even pre 0.1). It's a bummer I was in the middle of learning rust, so I wasn't of much help. Would've loved to contribute

Don't worry, you still can! I've been actively contributing to the past 4 months, working on improving CI and the website. I started out doing PRs for typos and little improvements, and so can you! (I recommend looking for issues marked as "Good-First-Issue," they are the best entry-level things to work on.)

Re: The Bevy Foundation

#26
I've been using Bevy recently so here are some thoughts on this:

Firstly, the overall quality is high and seeing this attention being paid to the project's organization is another good sign.

Documentation is not great. The Bevy book runs out of content very quickly. The "Cheat Book" has additional useful information: https://bevy-cheatbook.github.io/. With these plus the examples I've been able to figure out everything I need, but it's slow going.

I'm not 100% sold on ECS. It loses a lot of type safety and there doesn't seem to be any way to ensure cleanup of entities and their components.

Re: The Bevy Foundation

#27

I've been using Bevy recently so here are some thoughts on this: Firstly, the overall quality is high and seeing this attention being paid to the project's organization is another good sign. Documentation is not great. The Bevy book runs out of content very quickly. The "Cheat Book" has additional useful information: https://bevy-cheatbook.github.io/ . With these plus the examples I've been able to figure out everyth…

How does it lose type safety?

I was under the impression that bevy's Query system is type safe.

Post reply on HN