BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Google Native Client Content on InfoQ

News

RSS Feed
  • Google Is to Remove Support for PNaCl

    After de-staffing the PNaCL/NaCl team last year and adding default support for WebAssembly in Chrome in March of this year, Google has officially announced the retirement of PNaCl in favor of WebAssembly.

  • Both IE and Chrome Are to Support asm.js

    The modern.IE Platform Status indicates that now asm.js is in Development. According to Microsoft, the Chakra engine in Windows 10 will support asm.js, and Microsoft has been collaborating with Mozilla to implement it faster. Chrome is going to support it via TurboFan, a new optimizing compiler for V8.

  • Debate: Do We Need a Universal Web Bytecode?

    Is a universal web bytecode worth the trouble creating it? Is LLVM the solution? Which is better at running native code in the browser: Mozilla asm.js or Google PNaCl? This article contains opinions expressed on the web on these issues.

  • An Update on Google Native Client

    Beside C/C++, Google Native Client has added support for runtimes such as Mono, and a richer set of Pepper interfaces: accelerated 3D, full-screen, File IO, debugging, and others. New languages -Lua, TCL, OCaml- are being ported, and several major producers have ported their game engines or their games to NaCl.

  • Google Native Client Makes Its Debut in Chrome 14

    Google Native Client has been included in Chrome 14 Beta, on its way to become a technology supported in production.

  • Google Revamps Native Client, but will it be taking it all the way?

    About a year after it’s original announcement, Google released a new version of the Native Client (NaCl) SDK, which allows the safe execution of native code from a web browser. It is unclear though, if this ambitious project will be making it to production, or have the fate of other projects like Wave or Gears.

BT