Talin

I believe that @ickshonpe has previously expressed opposition to this approach. If I remember correctly, they believe that the proposed wrapper abstractions don't actually help all that much, and have...

Some more detail on this: As the person who (at this time) is the primary user of ghost nodes, I want to share my impressions. None of my uses of...

> The cursor position is transformed to local node space during picking so that it respects rotations and scalings. I'm not sure this solves the problem I have been having...

"A modern, high performance engine for games and graphical simulations, built in Rust with love" We've already mentioned the fact that people are motivated to come to Bevy because of...

I would cut the Disabling chapter entirely. However, I am biased here: I think the `Disabled` component is a blunt instrument which requires expertise to be able to use well...

Alternatively, if you really want to talk about disabling, then I would expand the scope of the chapter to talk about *all* of the ways you can disable an entity...

Also, I would seriously consider adding a "Beyond Bevy" section at the very end that talks about resources outside of the Bevy engine proper. This would include links to the...

Thinking about this some more, I would rename the "architecture" section to "modular design", and move the "states" section under "control flow".

Another idea: in the "What is Bevy?" section, add the following: ## Let's Get Serious Although Bevy bills itself as a game engine, you can use for other things than...

> I object to how dark the dark mode background is The problem is that without this change, there's just not enough contrast. The inline code sections don't stand out...