OK, so this isn't the first in-browser emulator we've seen, but we thought you might get a kick out of it anyway. Using Chrome's Portable Native Client (PNaCl), Google developer Christian Stefansen has the Universal Amiga Emulator (UAE) running within the browser.

Introduced in 2009, Google's Native Client (NaCl) started out as a way of running native x86 code in a safe, sandboxed environment. It uses specially compiled programs, combined with the x86 processor's built-in memory segmentation capabilities, to offer something like 95 percent of the performance of unsandboxed programs. An ARM version made its debut in 2010.

NaCl gets its performance—and the "native" part of its name—by using processor-specific code. x86, x64, and ARM are all currently supported, but programs must be compiled separately for each: ARM processors obviously cannot run x86 code, nor vice versa.

PNaCl addresses this. Instead of compiling programs to use x86, x64, or ARM code, they're instead compiled to use a bytecode—specifically, a version of the bytecode that the LLVM compiler uses to represent programs that it's compiling. These bytecode programs are then compiled into code appropriate to the user's processor within the browser.

If that sounds familiar, it should, as it's not a million miles away from how Java and .NET work: programs are compiled to bytecode, and the browser (or a plugin within the browser) converts it to native code on the client side.

The big difference is that the LLVM bytecode used in PNaCl is substantially lower level. The Java and .NET environments both provide a wide range of features such as extensive class libraries and garbage collected memory that PNaCl and LLVM do not. Java and (optionally, though on by default) .NET also restrict programs to only performing operations that are known to be safe, preventing certain traditional programmer bugs such as buffer overflows. PNaCl has none of these restrictions. Instead, it depends on the sandboxing system to provide security.

The Amiga-in-the-browser emulator uses the much-loved UAE emulator—around 400,000 lines of C—and PNaCl. Stefansen writes that the original port took four days, and "polishing" took at least four times longer than this port. Perhaps unsurprisingly from such a quick port, there are some bugs and feature omissions, though the emulator is still sufficient to give a taste of the Amiga experience.

PNaCl has not been universally embraced by the browser community, with both Mozilla and Opera criticizing it. Mozilla in particular has been backing asm.js and tuned JavaScript engines to provide near-native performance. The Amiga emulator does, however, demonstrate one advantage of PNaCl over asm.js: the emulator is multithreaded. Not a problem for PNaCI, but currently a big sticking point for the single-threaded asm.js.