[CaptainOfCoit]

> Your goal here is to make the best GITHUB OPEN SOURCE game engine possible.

That sounds awful if applied to Bevy, and seems you misunderstand what "Mr. Beast" is trying to say.

They're not saying make the best game engine, but make the game engine that would do best by GitHub-popular metrics, which is absolutely the wrong way to go.

I hope they continue to simply make the best game engine available, as before, and ignore useful metrics or focusing on where it's hosted.

[debugnik]

They didn't misunderstand, they're calling out Bevy's priorities.

Bevy is still incomplete as an engine. AFAIK there's only one commercially successful game made with it, Tiny Glade, and it doesn't even use Bevy's renderer but a custom one.

Yet the Bevy developers distract the project with essays and debates about the politics of their federated social media presence. You don't need that to build a game engine, but you do to build a "GITHUB OPEN SOURCE" game engine. I don't think there's anything inherently wrong with it, but that's clearly the focus here.

[CaptainOfCoit]

> They didn't misunderstand, they're calling out Bevy's priorities.

Yes, but the misunderstanding I'm trying to point out is that Mr Beast is not trying to create something of value, they're trying to create something that works well on a specific platform.

In the Bevy analogy, that would be creating a GitHub project that gets the most stars, regardless of how useful or well the engine itself is working.

I'm instead saying the same thing as you, they should continue focusing on building the greatest engine, regardless of the platform for hosting the project.

If Bevy were to follow Mr Beasts advice, they'd focus on flashy demos, engaging READMEs and so on, to increase the success on the platform itself, instead of focusing on the engine itself, which from following their direction almost since inception, they're doing a pretty good job with already.