Linked by Thom Holwerda on Thu 12th Dec 2013 23:17 UTC, submitted by anonymous
Amiga & AROS

This website runs an emulator of the Amiga 500 inside of Chrome by using Portable Native Client, a way to run existing C/C++ in the browser in a safe way across operating systems and across machine architectures. On the main page you can boot the Amiga, insert floppy disks, play the games, and generally pretend it's still the late 80s.

So cool.

Thread beginning with comment 578584
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Ones doesn't need Chrome
by jacquouille on Fri 13th Dec 2013 14:44 UTC in reply to "RE: Ones doesn't need Chrome"
Member since:

Cool! Much better. IMHO It's stupid to run native code on a web goes against the original idea of the web.

Indeed. Luckily it's not needed. There are compilers, like emscripten (based on LLVM/clang) that will translate C/C++ to a subset of JavaScript that it easy for JavaScript engines to compile to quite optimized machine code (see That's how e.g. Unreal Engine 3 was ported to JavaScript, running well. So I don't think that there is still a point in PNaCl (or NaCl).

Reply Parent Score: 4

RE[3]: Ones doesn't need Chrome
by reduz on Fri 13th Dec 2013 17:08 in reply to "RE[2]: Ones doesn't need Chrome"
reduz Member since:

Even with asm.js, emscripten runs like ass, performance is bad, resulting binaries are huge and decompressing them/parsing them takes a long time, a giant amount of ram, and freezes the browser.

Plus it does not support threads, streamed audio and all the other stuff PNaCL does.

PNaCL has more interesting uses right now, though, such as running on Google App Engine, Chromebooks and Providing an alternative framework for writing Android Apps.

Edited 2013-12-13 17:08 UTC

Reply Parent Score: 5

jacquouille Member since:

It's hard to reply to this comment due to the high number of factually, flat-out wrong statements there.

Performance is consistently within 2x of native for real-world cases such as Unreal Engine 3; resulting "binaries" are not significantly larger than machine code; RAM usage is only marginally higher than native; streamed audio is fully supported. Regarding "freezing the browser", feel free to file bugs if that happens for you.

Looking for a point in your comment, I found one: it is true that there is not yet a general solution to threading in the Web platform, as Web Workers are too limited. This is currently an area of active work by various browser vendors.

Reply Parent Score: 4