Native Client is a very complex framework that allows browsers to run native compiled code in a sandbox. Google's goal is to "maintain the OS portability and safety that people expect from web apps", while allowing developers to use their preferred language. Right now, the only supported languages are C and C++ and Native Client only works in Chrome for Windows, Mac and Linux.
"Native Client apps live on the web platform, so you don't need to create separate versions of your app for each operating system. Rather than relying on OS-specific APIs, Native Client apps use Pepper, a set of interfaces that provide C and C++ bindings to the capabilities of HTML5. This means that once you've ported your code to Native Client, it will work across different operating systems, and you only need to maintain one code base. Today Native Client supports the Pepper APIs for 2D graphics, stereo audio, URL fetching, sandboxed local file access (File API), and asynchronous message passing to and from JavaScript. In future releases we will be adding support for hardware accelerated 3D graphics (OpenGL ES 2.0), fullscreen mode, networking (WebSockets and peer-to-peer connections), and much more," informs Google.
Google announced that developers will be able to upload their native apps to the Chrome Web Store once Chrome 14 hits the stable channel. In the meantime, Chrome 14 users can try the examples from this gallery: a pi generator, a sine wave synthesizer and John Conway's Game of Life.
NaCl (Native Client) + Pepper -> a lot of games, business apps, educational apps, image editors and virtual machine software running inside your browser. Suddenly, Chromebooks are no longer that limited.
There are already much more complex examples of NaCl use on the net. For example in the link below you can find links to compiled Quake and Doom instances, meaning you can just open them in Chrome and play. For me, Quake never seemed to finish loading all the resources and stuck at loop demo of the game, but Doom runs just fine on Chrome 15.
ReplyDeletehttp://www.chromium.org/nativeclient/getting-started/native-client-in-the-wild
Ok, disregard that comment about Quake, it runs just fine as well, I didn't figure I had to press enter to get to the menu :)
ReplyDeletei cant get around give me back the other gmail please i dont like the chrome
ReplyDeleteKudos To Whomever Can Solve This
ReplyDeleteI've been tossing this around Google + since the beginning and so far I haven't gotten any real responses with suggestions. Yesterday I went through my Windows XP Registry and started removing all Google entries. I downloaded Chrome again and tried to install but the exact same error occurred.
I hope someone in this group of Techies will know how to solve it!
A few months ago I wanted to do a fresh install of Chrome, so I uninstalled. Only when I ran the new Chrome Setup.exe this is what I got instead:
Google Update Setup has encountered a problem and
needs to close. We are sorry for the inconvenience.
For more information about this error, click here.
Error signature
AppName: chromesetup.exe AppVer 1.3.21.79 ModName: sdhook32.dll
ModVer:2.0.5.1 Offset: 00034e67