Skip to content

RFC: Bevy vs flecs #891

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
andrewgazelka opened this issue Apr 28, 2025 · 0 comments
Open

RFC: Bevy vs flecs #891

andrewgazelka opened this issue Apr 28, 2025 · 0 comments

Comments

@andrewgazelka
Copy link
Member

andrewgazelka commented Apr 28, 2025

We are experimenting with moving to Bevy.

I could see this as a great way to join forces with Valence and potentially FerrumC. However, there are definitely going to be draw backs. I am making this issue to request for comments with respect to us moving to bevy. I have already outlined some potential issues that need to be resolved before we can move over.

Note this would not be our first architecture change. We used to use evenio. See:


https://discord.com/channels/1222556172385783890/1366122267930656920

note for my main issue (ugly gets Sander is willing to spend some time for our use case if we stay on flecs)

Image
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant