diesel_async VS bevy

So I want to use diesel_async in my web backend.

The already linked discussion from last time already contains a lot of information about this. Diesel itself does not provide async operations and that will likely remain that way for a foreseeable future. At least my preferred solution is to keep async support in a separate crate. A prototype for this is currently available here. Keep in mind that this is not released yet, so there might be bugs everywhere. I plan to cut a first release of this crate after the final release of diesel 2.0, which means hopefully soon. As for ETA's: I generally do not give any ETA's for releases, as this is currently a free time project for me.

So, diesel is an ORM that tries to take full advantage of rust's typing expressivity to allow for statically checked, and fast, queries. I absolutely loved it when trying it out the first time.

i don't see why you or anyone else would consider it too big of an issue that Diesel doesn't have async. For those who really want async diesel right now, the author already released diesel_async as a stop-gap solution, but even without that there's nothing wrong with using spawn_blocking. It feels worse than it really is to use blocking thread pools; until io_uring is a thing, there's no real getting around the necessity of threads being blocked for I/O and so adding async to the mix doesn't magically make things faster.

As for now there is an prototype available here. It's technically feature complete, but depends on a unpublished diesel version + has some remaining bugs with certain mysql versions. If that is fixed I will likely publish a first alpha version officially. That can take same time because that's a second large project that needs maintenance time beside diesel itself and that's quite a lot to do in my free time. You can support this work by sponsoring me on github

Async support for diesel currently lives in a separate repository as there are language level blocking issues for publishing a version of this crate where we could commit to a stable release at all. See the corresponding diesel issue for details.

https://github.com/weiznich/diesel_async tho'.

Weiznich (the maintainer of Diesel) has created an experimental async version of the diesel Connection and RunQueryDsl traits, which should help with ease-of-use for Diesel within async contexts. It is not yet published on crates, but you can find it here: https://github.com/weiznich/diesel_async

Bevy. A very young engine where you need to write the game entirely in Rust—that was appealing. But fatal flaws overshadowed everything: no editor, the engine brutally enforces the ECS approach, and the game's architecture must literally bend to fit this paradigm. So, you won't migrate to another engine at all—you just throw away all the code and start from scratch.

Missing one of the best choices as long as "maturity" isn't on the top of your list: Bevy - https://bevyengine.org/

Game engine written in Rust, leveraging ECS in almost every place and way, with a really capable WASM export option. Wrestling ECS for the first time might take you some time, but in my experience helps you keep game code as clean and decoupled as game code could be.

I don't see WASM/WebGPU changing anything when it comes to gaming, as an industry, personally. 3d visualizations and interactive websites? Yeah definitely a nice improvement over WebGL 2, if years late.

WebGPU is pretty far behind what AAA games are using even as of 6 years ago. There's extra overhead and security in the WebGPU spec that AAA games do not want. Browsers do not lend themselves to downloading 300gb of assets.

Additionally, indie devs aren't using Steam for the technical capabilities. It's purely about marketshare. Video games are a highly saturated market. The users are all on Steam, getting their recommendations from Steam, and buying games in Steam sales. Hence all the indie developers publish to Steam. I don't see a web browser being appealing as a platform, because there's no way for developers to advertise to users.

That's also only indie games. AAA games use their own launchers, because they don't _need_ the discoverability from being on Steam. So they don't, and avoid the fees. If anything users _want_ the Steam monopoly, because they like the platform, and hate the walled garden launchers from AAA companies.

(I work on high end rendering features for the Bevy game engine https://bevyengine.org, and have extensive experience with WebGPU)

I was working through an example in the repo for the Bevy game engine recently and came across this code

That's possible. I did spend quite a bit of time tinkering with compiler flags, and followed the recommendations.

Some notes I found just now seems to agree with my results, though: https://github.com/bevyengine/bevy/issues/3978#issuecomment-...

I cannot recommend immediate mode GUI programming based on the limitations I've experienced working with egui.

egui does not support putting two widgets in the center of the screen: https://github.com/emilk/egui/issues/3211

It's really easy to get started with immediate mode, it's really easy to bust out some UI, but the second you start trying to involve dynamically resized context and responsive layouts -- abandon all hope. The fact it has to calculate everything in a single pass makes these things hard/impossible.

... that said, I'm still using it for https://ant.care/ (https://github.com/MeoMix/symbiants) because it's the best thing I've found. I'm crossing my fingers that Bevy's UI story (or Kayak https://github.com/StarArawn/kayak_ui) become significantly more fleshed out sooner rather than later. Bevy 0.13 should have lots more in this area though (https://github.com/bevyengine/bevy/discussions/9538)

I've also been enjoying building My First Game™ in Bevy using ECS. The community around Bevy really shines, but Flecs (https://github.com/SanderMertens/flecs) is arguably a more mature, open-source ECS implementation. You don't get to write in Rust, though, which makes it less cool in my book :)

I'm not very proud of the code I've written because I've found writing a game to be much more confusing than building websites + backends, but, as the author notes, it certainly feels more elegant than OOP or globals given the context.

I'm building for WASM and Bevy's parallelism isn't supported in that context (yet? https://github.com/bevyengine/bevy/issues/4078), so the performance wins are just so-so. Sharing a thread with UI rendering suuucks.

If anyone wants to browse some code or ask questions, feel free! https://github.com/MeoMix/symbiants

These days, some game engines have done pretty well at making compute shaders easy to use (such as Bevy [1] -- disclaimer, I contribute to that engine). But telling the scientific/financial/etc. community that they need to run their code inside a game engine to get a decent experience is a hard sell. It's not a great situation compared to how easy it is on NVIDIA's stack.

[1]: https://github.com/bevyengine/bevy/blob/main/examples/shader...

This is the API you need: https://github.com/bevyengine/bevy/pull/9774