Re:Show HN: An NES emulator written in Rust
by gnuvince on Sunday February 10, 2013 @12:31AM
(#5195541)
I guess it depends on how closely you want to emulate the platform. For example, there was a great article [1] about a SNES emulator that required an extremely powerful machine, because it aimed to be a 100% accurate emulator. I guess if pcwalton decides to go for a very accurate NES emulator, the CPU usage would be non-negligable.
[1] http://arstechnica.com/gaming/2011/08/accuracy-takes-power-o...
Re:Show HN: An NES emulator written in Rust
by jthomp on Sunday February 10, 2013 @12:54AM
(#5195584)
Nice, I was about to link the same thing.
Re:Show HN: An NES emulator written in Rust
by pcwalton on Sunday February 10, 2013 @03:05AM
(#5195783)
You're right, it's a silly statement. Because you don't need to run more than 60 frames per second, you won't start seeing performance degradation over native until you hit, say, 10X slower than optimized C.
What I was getting is that I think turning off the frame limiter and counting how many frames run in, say, 10 seconds would be a nice benchmark of compiler optimization.
Re:Show HN: An NES emulator written in Rust
by kibwen on Sunday February 10, 2013 @12:31AM
(#5195535)
I think you're missing the point. From the README:
"Its purpose is to serve as a technology demonstration to show how the Rust programming language is suitable for systems software such as emulators. [...] sprocketnes is also designed to be a relatively clean example codebase, showing off various Rust idioms."
Since when does an NES take "decent processing power" to emulate? I emulated NES games on a 386DX40 and SNES games on a 486DX266. Certainly the emulation wasn't as accurate as what you get today, but neither is this tech-demo example.