macroquad VS rust_minifb

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.

Well, it depends on how you use it; writing to an image buffer isn't much less efficient than writing to any normal buffer (in fact, although displaying your scene to a window efficiently is important, your main bottleneck will be the actual ray tracing loop). You may want to read this article for a practical example of using an ImageBuffer to create and draw a texture with Piston. Other window backends you could use, apart from pixels which was already mentioned in another comment, include minifb and Mini GL, though I haven't personally used them.

After watching the Numberphile video on this formula, I decided to implement it in Rust for fun. It uses minifb for the window creation + framebuffer.

Before I could implement the display output, I needed something to draw the images onto. There are quite a few Rust crates available to create a GUI window and update it with 2D graphics. Most of these are of course intended for making games, and also include ways of getting key presses as input, which I'll also need. I looked at Piston, which I've used before on other projects, Macroquad, which also supports web assembly as well as desktop targets, Pixels, which is intended specifically for 2D games, and Minifb, which is also specifically for 2D applications, but is much simpler. I also tried out libretro, which is specifically made for video game emulation, but I found it much more restrictive than the others because of it's narrow focus.

There's several different approaches you could take, but I'd probably suggest macroquad as the easiest. I've also used minifb for windowing + a drawing library like raqote or tiny-skia.

I don't know much about Rust, but I used the C version this library, and I think this is as simple as it gets: Rust MiniFB. Hope this helps

A very simple color manipulation library backed by a u32. My use-case was for use with minifb which uses a u32 frame buffer. Feedback appreciated.

If all you need is a pixel/frame buffer I'd suggest either pixels-rs or minifb.

In my experience, it really makes no difference what rendering backend you use for something as simple as a NES emulator. The 'pixel_renderer' that i wrote basically does the simplest possible thing i could think of - it takes a pixel buffer in cpu memory, copies it over to the gpu, turns it into a texture and stretches it to cover the entire screen. There seem to be many crates out there that do just this - my choice to roll my own was really one out of curiosity and completionism more than anything.