The update at the bottom is kind of interesting. All browsers are equally fast, which makes sense because wasm should speak directly to the hardware more easily than javascript.
It is slow it is rarely used it doesn't get optimized it is slow
When looking at emulator benchmarks it's always important to also look at how the emulator has been implemented, and what compromises an emulator might make to balance between performance, accuracy and "design purity" (e.g. the cycle-stepping CPU model isn't all that useful in practice, except that it is 'more pure' and interesting from an emulator-design point-of-view). In comparison to those implementation differences, the performance difference between WASM and JS should be mostly negligible.
http://8bitworkshop.com/docs/_images/js-vs-wasm-1.jpg
Inhumanly abstract, yet intriguing.
No link in the article, and I wasn't able to find a public project that tries to do this. Is there?
http://8bitworkshop.com/docs/posts/2021/8bitworkshop-release...
IDE: https://8bitworkshop.com/v3.10.0/?file=clock_divider.v&platf...
:D
https://8bitworkshop.com/v3.10.0/?file=tank.v&platform=veril...