Alexander

Yeah, I actually worked with a guy who thought it’s all a bunch of noncense, and made really harsh jokes about typesafety and ownership rules and such, yet delivered decent Rust code!

On the other hand, bevy is such a neat general manager and framework. You can run crossplatform parallel async within it, stall things with timers, set custom loop rates. I’m experimenting with using it as non-game frontend, and so far it seems much more suited for fast development than those reactive frameworks imitating js frameworks if something more complicated than simple ui is needed. The gaming community cares for each othes, so sweet. The only downside is 30mb wasm file for prototype level of complexity app, but I haven’t even started optimizing yet, and it will not grow much probably once it becomes super sophisticated.

Even disconnected and incredibly diverse, united only by the tool, it’s still a community. After all, we have more in common than some nations! (I still actively think there are fractions of community I hate, and more I don’t know about and don’t care to know about, but those are parts of social life too, I guess)

And when we talk about abstract constructs like communities, there is no need for conscious will or organizing initiatives. It just happened, just remember to disregard anyone talking about actual organized Rust community as having an authority or something; rationale behind the design principle is the only organizing entity here it seems.

That people create conspiracy theories whenever self-organization happens is natural thing apparently, you can’t do anything about it. It’s narration knowledge in a sense, and in our postmodern world, it is no more justified than solid scientific model of the world, we just have to accept and live around it, trying to avoid feeding myths is futile.

Use Bevy with egui, just disable needless features. You’ll get performance hit until there is an actual complete game inside.

GUI is just a mess. I think bevy is to-go though, it could be tuned a lot to turn down memory demand. Otherwise, use system level stuff, like web-based ui or Qt wrap.

At least that’s what I ended up thinking after struggling with same question.

no no_std?

This is so true! Tried “nice crossplatform WASM” multiple times - every time you need a system call, drawing single pixel, networking, or catching input - you just start debugging JS. If the logic is simple, whole code ends up being JS mess with small inclusions of Rust. Very unpleasant experience, even with all the modern frontend code generator tools.

I ended up deciding that making custom bindings instead (edit: mention uniffi here) and building frontend in native (Qt/Kotlin/Swift) ends up being simpler, more pleasant, and the end result is faster and prettier (and no wasm limitations). The downside is having to actually use XCode if you do want iOS app to work (which is quite simple but unpleasant and requires you to have Apple hardware or suffer a lot), but if not and you don’t care for Apple worshipers - it’s pure win.

Even 2 years ago, yew was way way worse than actually writing js by hand.