macroquad VS wasm-pack-template

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.

. ├── Cargo.toml ├── package.json ├── examples │   └── hello-world // React project initialized by vite ├── packages │   ├── react // WASM project created by cargo generate --git https://github.com/rustwasm/wasm-pack-template │   ├── react-dom // WASM project created by cargo generate --git https://github.com/rustwasm/wasm-pack-template │   ├── react-reconciler // Rust project created by cargo new │   └── shared // Rust project created by cargo new

I use this https://github.com/rustwasm/wasm-pack-template

Ah, it looks like it requires for tests to be prepended with #[wasm_bindgen_test]; not sure if this will help you, then :-//

The first tutorial step focuses on the setup. It's short and is the most "copy-pastey" of all. The reason for that is that it leverages cargo-generate, a Cargo plugin that allows creating a new project by using an existing Git repository as a template. In our case, the template is a Rust project ready to compile to Wasm. The project's structure is: