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."
Thread beginning with comment 463400
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: A new OS paradigm?
by Neolander on Sun 20th Feb 2011 21:09 UTC in reply to "A new OS paradigm?"
Member since:

Until the internet connexion starts to fail, that is...

However, that's already a problem with vanilla ChromeOS

Edited 2011-02-20 21:10 UTC

Reply Parent Score: 1

RE[2]: A new OS paradigm?
by Morgan on Sun 20th Feb 2011 21:18 in reply to "RE: A new OS paradigm?"
Morgan Member since:

Yeah, that's my biggest issue with this "online OS" trend too. I think it's all a bit premature until we achieve a state of ubiquitous wireless network connectivity that is as robust and failsafe as the current physical interconnects on the motherboards and processors of today. Not to mention the bandwidth required for full network only computing.

I have a feeling that is a long way off.

Reply Parent Score: 3

RE[3]: A new OS paradigm?
by Lennie on Sun 20th Feb 2011 21:56 in reply to "RE[2]: A new OS paradigm?"
Lennie Member since:

I keep hearing this, but you don't need an internet connection for HTML-apps after the initial download.

You have local-storage, session-storage, indexedDB and more importantly HTML5-app-cache and offline-API:

And things like the Canvas-API which allows you to manipulate images in the browser without uploading them to the server. You can choose an image from disk and instead of uploading it to the server manipulate it in the browser first. Maybe even just save it locally.:

Like the red-eye removal demo:

Or how about a webmail site that caches all your emails locally so you can read them when there is no connection and even save emails to be sent later.

Edited 2011-02-20 22:00 UTC

Reply Parent Score: 6

RE[2]: A new OS paradigm?
by Radio on Mon 21st Feb 2011 14:43 in reply to "RE: A new OS paradigm?"
Radio Member since:

On the other hand, having everything synced live is also nice, in case the "local" hardware fails...

There is an interesting article today in the french newspaper "Le Monde" about how the video website Bambuser was the favorite way to share videos amongst Egyptian during the revolution: with this website, you stream the live video (and the website keeps it for future replays), which means even if the police catches you and takes away and destroys your cellphone, the video is already safe on a server...

Reply Parent Score: 3

RE[3]: A new OS paradigm?
by Neolander on Tue 22nd Feb 2011 06:51 in reply to "RE[2]: A new OS paradigm?"
Neolander Member since:

This is an interesting debate. Sure, you're right that in this case, having the live video stream synced online in real time was the best way to keep the video in safety.

On the other hand, while it works perfectly well for videos with low popularity, I think "breaking" news should not be distributed this way, if the guy cares a bit about his life. Considering how easy it is to locate a cellphone geographically nowadays, including when the guy has gone back home and forgotten to turn it off because he feels in safety, I think that things like sharing the video via freenet later, from a safe place with the lot of time it takes, would be a much better idea.

Edited 2011-02-22 06:53 UTC

Reply Parent Score: 1