gameboy VS actix-todo

Looks like they used an existing emulator and this was mostly a hardware and memory integrity test. I’d love to see this approached from the perspective of “how clever can we get with the emulator itself to save power?”

When I wrote mine, something I ran into was realizing that often the CPU and PPU are just doing the same thing over and over and over. If only I could cache all that work.

For example, you don’t modify the previous frame. You have to draw the entire frame every time, writing sprites from OAM memory every time. Sometimes games do clever stuff here for effects, but a lot of the time you’re just drawing the same stuff. Like Tetris is almost completely a routine of drawing almost entirely the same graphics every time. Most of the cycles and OAM writes are just juggling sprites to draw the same layout every time.

I documented the heck out of the PPU because it gave me the second most grief (sound being the worst by far) if you are curious: https://github.com/ablakey/gameboy/blob/master/src/guest/sys...

As long as you're not doing any complex argument handling, it's dead simple:

https://github.com/ablakey/gameboy/blob/master/src/main.rs#L...

Here is one built with actix-web that I have looked at

https://github.com/nemesiscodex/actix-todo

My advice is pick a http server that you want to use and search github for Cargo.lock