Linked by fran on Sun 20th Feb 2011 19:00 UTC
Google "Over the last few months we have been hard at work getting Native Client ready to support the new Pepper plug-in interface. Native Client is an open source technology that allows you to build web applications that seamlessly and safely execute native compiled code inside the browser. Today, we've reached an important milestone in our efforts to make Native Client modules as portable and secure as JavaScript, by making available a first release of the revamped Native Client .[...]In the coming months we will be adding APIs for 3D graphics, local file storage, WebSockets, peer-to-peer networking, and more. We'll also be working on Dynamic Shared Objects (DSOs), a feature that will eventually allow us to provide Application Binary Interface (ABI) stability."
Permalink for comment 463476
To read all comments associated with this story, please click here.
RE[3]: A new OS paradigm?
by jabjoe on Mon 21st Feb 2011 11:14 UTC in reply to "RE[2]: A new OS paradigm?"
Member since:

ARM isn't one target. It's many. Different versions of the instruction set, with and without different extensions. That's why open source is so great, this doesn't matter. x86 need the backwards compatibility because it's a closed platform, things can't be recompiled. ARM has never had the need to be static like this, not since it left Acorn behind. Each device can have the ARM as it requires and code compiled for that. In open source world, this doesn't matter either, a repository is just compiled against the target for that device/family.

I still don't get what the big deal is about online apps vs a repository. Locally installed apps, updated from the "main frame", isn't this what locally installable cloud apps are? Non locally installed cloud apps are useless because you won't always have a connection, let alone a good one. So actually, I'm quite happy as is.....

Reply Parent Score: 3