4 ms·

I am wondering how the emulator performs. JS seems not a right language for this kind of tasks.

• danneu 14y ago
  Did you visit the website? JS isn't chosen for explicit performance. It's chosen because it can sit in a browser.
• nandemo 14y ago
  Think about it. Nintendo 64 was released around 15 years ago. Its CPU was somewhat slower than the CPUs that typically run modern browsers.
  • heretohelp 14y ago
    Think about it. You need a 3ghz machine just to emulate the SNES accurately. With C++. Doing an N64 in JS will not work.
  • shinratdr 14y ago
    Processor speed is near irrelevant. The processors that ended up in gaming consoles are both extremely complex and unique. More important than that, they were pushed to the absolute limit using specific programming tricks that work only on that processor by devs that had the official Nintendo dev kit. Not to mention full documentation, upwards of 5+ years of dev experience with that specific console, while also surrounded by people who know the ins and outs of the console better than Nintendo. Emulating an N64 will continue to be difficult long after x64 processors have outstripped it in terms of speed by hundreds and hundreds of times. It will continue to require an HLE design to be playable until even after that. Then, maybe after we have an LLE N64 emulator, HLE JS N64 emulation will be within the realm of playable.