ggez VS quicksilver

I'd say to use either https://macroquad.rs/ or http://ggez.rs/, they're both basically "all that you need for 2d". I've used macroquad extensively, but that was mainly because ggez was undergoing a big rewrite to wgpu which is now complete with 0.8.

ggez also looks pretty straightforward and simple to get graphics moving around quick and easy.

https://github.com/ggez/ggez/issues/1158 For this is it as simple as changing the methods to take &Image, .clone() it inside and use that or is cloning missing the point of the change?

Sounds like https://ggez.rs/.

Nice, can you add it to the list of projects https://github.com/ggez/ggez/blob/master/docs/Projects.md ?

ggez simple example (not working): https://github.com/ggez/ggez/tree/master/examples/01_super_simple.rs ggez bunnymark (works in batched mode only): https://github.com/ggez/ggez/blob/master/examples/bunnymark.rs wgpu example (working): https://github.com/gfx-rs/wgpu/tree/master/wgpu/examples/hello-triangle

I’ve used https://ggez.rs for side projects and have been happy with it.

Another simple 2d framework that targeted wasm and desktop was https://github.com/ryanisaacg/quicksilver but unfortunately it was abandoned :( and never had android support.

quicksilver, though not really being developed anymore is still pretty good.

Thanks! I'm currently not using an engine, it's all done "from scratch". None of the available engines quite had the WASM support I wanted. I started with Quicksilver but it was not flexible enough and it is no longer actively developed.

quicksilver is a simple framework you can use. Sadly the main developer stopped working on it (PR's are still accepted though) but it is still pretty solid. It also has WASM as first class support and thus makes sure that its api is a good fit for the limitations that browsers put on code. (So, loading assets is async, your main loop is done using async, etc).