Google offers a new way to run applications in Chrome (browser) and potentially in Chrome OS: Native Client. Proposed as the NaCl, the SDK compatible with Chrome 10 in its beta version allows to run applications built with languages lows (and powerful) as C or C + +, without going through high-level languages like Javascript.
In practice, Google reinvents say Microsoft's ActiveX. NaCl is quite limited, applications running in a reserved memory area, without access to the system (principle of the sandbox) and through APIs to communicate with the browser. The idea is to allow applications to heavy computations on the CPU without using javascript (slow) and even - eventually - to access the graphics card, the sound card, etc..
For now still in testing, this system should eventually offer applications that run in a browser with performances close to the more conventional applications. For those wanting to try NaCl must activate it by typing "about: flags" in the address bar of Chrome 10 beta, of course, after you download it.
In practice, Google reinvents say Microsoft's ActiveX. NaCl is quite limited, applications running in a reserved memory area, without access to the system (principle of the sandbox) and through APIs to communicate with the browser. The idea is to allow applications to heavy computations on the CPU without using javascript (slow) and even - eventually - to access the graphics card, the sound card, etc..
For now still in testing, this system should eventually offer applications that run in a browser with performances close to the more conventional applications. For those wanting to try NaCl must activate it by typing "about: flags" in the address bar of Chrome 10 beta, of course, after you download it.
- Google's Native Client updates to Pepper API, looks set to fragment the Web (21/02/2011)
- With 'Arctic Sea,' Google offers a Web-app boost (18/02/2011)
- With 'Arctic Sea,' Google offers a Web-app boost (18/02/2011)
- With 'Arctic Sea,' Google offers a Web-app boost (18/02/2011)
- Secret-key single-message authentication: crypto_onetimeauth (21/02/2011)
No comments:
Post a Comment