rust-sdl2 VS macroquad

I don't think that SDL and WGPU are really comparable. You'd be better off comparing SDL to something like Notan or even the SDL bindings for Rust. That said, SDL will have vastly more learning resources than Wgpu or Notan or any Rust alternative. If you know and like rust you can probably use the resources with the Rust SDL bindings.

Those are 3 very different libraries. Are you looking for something in the middle, or do you want all of the features you described? For what it's worth, there's SLD2 bindings for Rust https://github.com/Rust-SDL2/rust-sdl2

There's already a Rust binding for SDL2. See https://crates.io/crates/sdl2

nope. https://github.com/Rust-SDL2/rust-sdl2/issues/884 emscripten target won't work yet either.

it seems like what you are looking for is sdl2 bindings

Dude. It's literally at most 50 lines of code, the entire project. What kind of documentation do you expect me to write? The library I'm using is this one. I don't know why you'd need to know anything about it since it's purely something that can appear literally anywhere, it's part of the language.

*and* SDL2-sys *and* Rust-SDL2

The SDL2 crate had something like this, and it's an option I'm considering. However, if possible, I'd prefer a different, simpler GUI library, so if there's an input-specialized crate out there that does this, I'd love it.

See the macroquad docs for full details on building a WASM game.

Any opinion on ggez? I don't like how everything in macroquad is global state https://github.com/not-fl3/macroquad/issues/333

I prefer examples like the ones in Macroquad: https://github.com/not-fl3/macroquad/tree/master/examples. I'm not against advanced examples, but the priority should be extremely clear, minimal, self contained ones.

There were even discussions about deprecating static mut. Even if you think you got it right, there are too many things that might go wrong, like aliasing. For example, macroquad needs a complete rewrite because of their static mut.

It's based on macroquad and you can play the wasm version here: https://unvirtual.github.io/yinsh-rs/

The reality is that I have used unsafe that is also unsound out of convenience because fixing it is a papercut too many. And this tends to be common! I know enough to spot unsoundness in other projects (sometimes even early). But not enough to be confident in my own abilities to write sound unsafe code. Why? Because it's really flipping hard, that's why!

Given that you are making a game, you might want to consider using a game framework such as https://github.com/not-fl3/macroquad/.Macroquad has full support for WASM, and will allow you to render your game both locally and in the browser via WASM depending on how you compile it.