Native Client (NaCl), Google's attempt at bridging the gap between pure JavaScript Web apps and installed programs, creeps ever closer to a stable release, and ultimate inclusion in other browsers, including Firefox. The plug-in, which allows the browser to safely execute native compiled code, has retired its NPAPI interface in favor of Pepper (PPAPI), and now has a much-improved SDK.NaCl, as a concept, is awesome. It allows for untrusted code to be executed natively, which is perfect for processor-intensive tasks like games and data analysis. The ultimate goal is to have NaCl modules that you can plug into a website, just like JavaScript is used at the moment -- a physics module, a maths module, a graphics module. JavaScript would still manage the easier bits, while NaCl would be leveraged for meatier tasks.
Ultimately, however, NaCl could cause immeasurable damage to the Open Web paradigm. NaCl is an open source project, but it still brings the same risks of fragmentation as Flash, Silverlight and Java applets. As it stands, only Chrome supports the Pepper interface that NaCl requires -- and with IE9 and Firefox 4 only weeks away from release, it would be a long time until support for the plug-in could improve.
If NaCl gains enough traction, Chrome could become the next IE6...
Continue reading Google's Native Client updates to Pepper API, looks set to fragment the Web
Google's Native Client updates to Pepper API, looks set to fragment the Web originally appeared on Download Squad on Mon, 21 Feb 2011 06:55:00 EST. Please see our terms for use of feeds.
Permalink | Email this | Comments
ELECTRONIC DATA SYSTEMS ELECTRONIC ARTS ECLIPSYS EASTMAN KODAK CO EARTHLINK
No comments:
Post a Comment