Slashdot Mirror


Google Native Client Puts x86 On the Web

t3rmin4t0r writes "Google has announced its Google native client, which enables x86 native code to be run securely inside a browser. With Java applets already dead and buried, this could mean the end of the new war between browsers and the various JavaScript engines (V8, Squirrelfish, Tracemonkey). The only question remains whether it can be secured (ala ActiveX) and whether the advantages carry over onto non-x86 platforms. The package is available for download from its Google code site. Hopefully, I can finally write my web apps in asm." Note: the Google code page description points out that this is not ready for production use: "We've released this project at an early, research stage to get feedback from the security and broader open-source communities." Reader eldavojohn links to a technical paper linked from that Google code page [PDF] titled "Native Client: A Sandbox for Portable, Untrusted x86 Native Code," and suggests this in-browser Quake demo, which requires the Native Code plug-in.

1 of 367 comments (clear)

  1. Re:doesn't sound too secure yet by Billly+Gates · · Score: 0, Troll

    Thanks to Microsoft's known influence to corrupt all the standard bodies the "(applet)" tag is now depreciated. ITs been depreciated since html 3 last century. (forgive the lack of brackets as Slashdot's garbage filter will cut them out)

    In essence I am guessing html tidy and other web authoring tools declare java objects as errors as applets are no longer part of the html standard.

    I am still mad that MS did this and it killed java overnight as IE has 90% marketshare at the time so everyone ran away from it fearing IE would not accept an applet tag anymore.

    I wish we can add applet or other tags back into the standards bodies so web designers wont be so afraid to use it.