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 463449
To read all comments associated with this story, please click here.
RE[3]: Comment by moondevil
by kaiwai on Mon 21st Feb 2011 05:03 UTC in reply to "RE[2]: Comment by moondevil"
kaiwai
Member since:
2005-07-06

I would argue that the flaw with Flash has less to do with the fact that you can't go 'view source' and more to do with the fact that it is a closed source implementation where there is no ability for a consortium of companies working on a single open source code base to fix up long standing issues with said technology.

Compare NaCL to Flash - NaCL is completely open sourced, the NAPI Pepper extensions are full open source as well. What does that mean as an end user? it means that if there are issues I'm not dependent on one single company to actually fix the problem in the case of Flash. If the Flash plugin was open source do you really think that the long standing issues would have existed if it meant that RedHat/Novell/Apple/etc were able to fix their platform specific issues?

You may talk about openness but for the majority of people they really don't care - what they care about is the end result and whether the end result is desirable. The issues with Flash had less do with 'open ness' as so far as being able to peak into raw source code and everything to do with the plugin being closed source and everyone dependent on one single company to fix issues.

Reply Parent Score: 3