And even then, I haven't benchmarked myself, but I wouldn't be surprised most NES emulators written in C or other native languages out there would do way more than 150FPS.
Edit: and it doesn't really matter either way because while useful, optcarrot is a very different workload from what Ruby is generally used for.
very different workload from what Ruby is generally used for.
Ruby is generally used for a lot of things, including scientific computing. I'm using it to process sound and make videos about sound, for example. Audio processing isn't too far off from the type of hot loop an emulator would have, so I hope to see benefits from YJIT in my own work, and will also try TruffleRuby once I've finished my current round of video editing.
Who cares if they do more than 150 FPS, when humans cannot see more than 60 FPS, unless we are talking about VR, which is nonsense for a NES emulator anyway.
Trying to win the benchmarks game makes people lose sight from what actually matters.
SPA would never had taken off if it wasn't for the work done in JavaScript JITs.
Similarly, Ruby JITs can open doors for just being the language used for Rails applications.
> Who cares if they do more than 150 FPS, when humans cannot see more than 60 FPS
Things in 120 FPS feels smoother than in 60 FPS. Less than 60 compared to 30, but it's still noticable. I don't know the exact mechanism, but I suppose that's because the real world has no concept of FPS and what we see is continuous, so our eyes are used to seeing something like this.
Back in the day, I used JRuby because it was the only way I was able to run Ruby on Windows 2003 servers that I was forced to use while working for the Federal Government. (Yes, Thin and Mongrel existed, but their perf on Windows was REALLY bad)
Was it fast? No. Was it "good enough?" yep. It never fell over.
