Google Brings AmigaOS to Chrome Via Native Client Emulation

First time accepted submitter LibbyMC writes "Google's approach to bringing older C software to the browser is demonstrated in bringing the '80s-era AmigaOS to Chrome. 'The Native Client technology runs software written to run on a particular processor at close to the speeds that native software runs. The approach gives software more direct access to a computer's hardware , but it also adds security restrictions to prevent people from downloading malware from the Web that would take advantage of that power.'" Chrome users can go straight to the demo.

Comments

80's hardware

[phrostie]

So an emulator running on 2010 era hardware can almost run at speeds of the native technology on 80's era hardware.

wow

Re:80's hardware

[michelcolman]

It's emulating Windows instead of AmigaOS?

Give me a damn web browser

[bobbutts]

If I want an emulator, I'll get an emulator.

Re:Give me a damn web browser

[vastabo]

This is Google demonstrating that their platform for abstracting a client's hardware is robust and performant. I suspect that Amiga emulation is just because it's cool.

Having this layer of abstraction protects Google from the machinations of software vendors who might want a piece of their action.

Re:Give me a damn web browser

[RabidReindeer]

This is Google demonstrating that their platform for abstracting a client's hardware is robust and performant. I suspect that Amiga emulation is just because it's cool.

No, It's just so you can play Lemmings the way it was meant to be played.

Re:So Great OS ran on top of crappy OS?

[cervesaebraciator]

Irregardless of what you say, "should of" works for all intensive purposes. Pacifically when writing informally, anyways. What else is one suppose to do in this case and point?

Lack of vision

[mcrbids]

Sometimes, Google just baffles me. The lack of direction in their product lines makes me shake my head.

We have several distinct software platforms:

1) Android. Development in XML with Java used as glue to hold everything together. Unless you don't. You can use standard C libraries and call the Linux kernel directly, bypassing the Dalvik Java VM.

2) Chrome browser. Development largely in javascript, again there are some obvious exceptions. Javascript is, of course, preferred because it's safer, so ChromeOS protects you by having everything done in Javascript. Except that it isn't.

3) ChromeOS. Kinda/Sorta like using the Chrome browser, except that it's not, because you are developing things that run as if they were actual clients. In Javascript. And of course, this too, is just as strictly enforced.

4) But Let's not forget the 4th platform in the trio: Google's Go language is clearly a contender, and it's designed to replace C, except for a few bone-headed decisions like linking everything statically resulting in enormous binaries. Because you really, really need to have the same library installed once for every app installed, because that way you get to recompile everything installed on your system any time a security update comes out for your favorite library. Except that, of course there are exceptions here, too.

And most importantly, you cannot target all these platforms with any single codebase written in any language. It's like they are trying to make their product suite as difficult as just using products from multiple vendors anyway.