1. Overview

2. Pepper
    PPAPI   PPAPI in Firefox  

3. Applications

4. Reception
    Supporters  Detractors 

5. Second Generation

6. See also

7. References

8. External links
    Examples 

To demonstrate the readiness of the technology, on 9 December 2011, Google announced the availability of several new Chrome-only versions of games known for their rich and processor-intensive graphics, including Bastion (no longer supported on the Chrome Web Store). NaCl runs hardware-accelerated 3D graphics (via OpenGL ES 2.0), sandboxed local file storage, dynamic loading, full screen mode, and mouse capture. There are also plans to make NaCl available on handheld devices.^[5][6]

Portable Native Client (PNaCl) is an architecture-independent version. PNaCl apps are compiled ahead-of-time. PNaCl is recommended over NaCl for most use cases.^[7] The general concept of NaCl (running native code in web browser) has been implemented before in ActiveX, which, while still in use, has full access to the system (disk, memory, user-interface, registry, etc.). Native Client avoids this issue by using sandboxing.

An alternative of sorts to NaCl is asm.js, which also allows applications written in C or C++ to be compiled to run in the browser (at more than half the native speed), and also supports ahead-of-time compilation, but is a subset of JavaScript and hence backwards-compatible with browsers that do not support it directly. Another alternative (while it may initially be powered by PNaCl) is WebAssembly.

On October 12, 2016, a comment on the Chromium issue tracker indicated that Google's Pepper and Native Client teams had been destaffed.^[8] On May 30, 2017, Google announced deprecation of PNaCl in favor of WebAssembly.^[9] Although initially Google planned to remove PNaCl in first quarter of 2018,^[9] the removal is currently planned in the second quarter of 2019 (except for Chrome Apps).^[10]

Overview

Native Client is an open-source project being developed by Google.^[11] To date, Quake,^[12] XaoS, Battle for Wesnoth,^[13] Doom,^[14] Lara Croft and the Guardian of Light,^[15] From Dust,^[16] and MAME, as well as the sound processing system Csound, have been ported to Native Client. Native Client has been available in the Google Chrome web browser since version 14, and has been enabled by default since version 31, when the Portable Native Client (PNaCl, pronounced: pinnacle) was released.^[17][18][19]

An ARM implementation was released in March 2010.^[20] x86-64, IA-32, and MIPS are also supported.

To run an application portably under PNaCl, it must be compiled to an architecture-agnostic and stable subset of the LLVM intermediate representation bytecode.^[21] The executables are called PNaCl executables (pexes). The PNaCl Toolchain makes .pexe files; NaCl Toolchain .nexe files. The magic number of .nexe files is 0x7F 'E' 'L' 'F', which is ELF. In Chrome, they are translated to architecture-specific executables so that they can be run.

NaCl uses software fault detection and isolation for sandboxing on x86-64 and ARM.^[22] The x86-32 implementation of Native Client is notable for its novel sandboxing method, which makes use of the x86 architecture's rarely used segmentation facility.^[23] Native Client sets up x86 segments to restrict the memory range that the sandboxed code can access. It uses a code verifier to prevent use of unsafe instructions such as those that perform system calls. To prevent the code from jumping to an unsafe instruction hidden in the middle of a safe instruction, Native Client requires that all indirect jumps be jumps to the start of 32-byte-aligned blocks, and instructions are not allowed to straddle these blocks.^[23] Because of these constraints, C and C++ code must be recompiled to run under Native Client, which provides customized versions of the GNU toolchain, specifically GNU Compiler Collection (GCC), GNU Binutils, and LLVM.

Native Client is licensed under a BSD-style license.

Native Client uses Newlib as its C library, but a port of GNU C Library (GNU libc) is also available.^[24]

Pepper

NaCl denotes sodium chloride, common table salt; as a pun, the name of pepper was also used. Pepper API is a cross-platform, open-source API for creating Native Client modules.^[25] Pepper Plugin API, or PPAPI^[26][27] is a cross-platform API for Native Client-secured web browser plugins, first based on Netscape's NPAPI, then rewritten from scratch. It is currently used in Chromium and Google Chrome to enable the PPAPI version of Adobe Flash^[28] and the built-in PDF viewer.^[29]

PPAPI

On 12 August 2009, a page on Google Code introduced a new project, Pepper, and the associated Pepper Plugin API (PPAPI),^[30] "a set of modifications to NPAPI to make plugins more portable and more secure".^[31] This extension is designed specifically to ease implementing out-of-process plugin execution. Further, the goals of the project are to provide a framework for making plugins fully cross-platform. Topics considered include:

• Uniform semantics for NPAPI across browsers.
• Execution in a separate process from the renderer-browser.
• Standardize rendering using the browser's compositing process.
• Defining standardized events, and 2D rasterizing functions.
• Initial attempt to provide 3D graphics access.
• Plugin registry.

The continuously evolving Pepper API also supports Gamepads (version 19) and WebSockets (version 18).^[32]

PPAPI in Firefox

Mozilla Firefox stated in 2014 that they would not support Pepper, as there is no full specification of the API beyond its implementation in Chrome, which itself is designed for use with Blink layout engine only, and has private APIs specific to the Flash Player plugin which are not documented.^[34] In October 2016 Mozilla announced that it had re-considered and was exploring whether to incorporate the Pepper API and PDFium in future releases of Firefox,^[35] however no such steps were taken.

Applications

One website^[36] uses NaCL on the server to let users experiment with the Go programming language from their browsers.^[37]

Reception

Some groups of browser developers support the Native Client technology, but others do not.

Supporters

Chad Austin (of IMVU) praised the way Native Client can bring high-performance applications to the web (with about 5% penalty compared to native code) in a secure way, while also accelerating the evolution of client-side applications by giving a choice of the programming language used (besides JavaScript).^[38]

Detractors

Other IT professionals are more critical of this sandboxing technology as it has substantial or substantive interoperability issues.

Mozilla's Christopher Blizzard criticized NaCl, claiming that native code cannot evolve in the same way that the source code-driven web can. He also compared NaCl to Microsoft's ActiveX technology, plagued with DLL Hell.^[3]

Second Generation

Second Generation of Sandboxing developed in Google is gVisor.^[41][42] It is intended to replace NaCl in Google Cloud, to be more exact in Google App Engine.

See also

• Application virtualization
• Emscripten
• Sandboxie, running Windows programs in a sandbox
• WebAssembly, a bytecode standard for web browsers
• XAML Browser Applications (XBAP)

References

External links

• {{Official website|https://code.google.com/p/nativeclient}}, Google Project
• {{Official website|https://developer.chrome.com/native-client}}, developers
• {{YouTube|id=5RFjOec-TI0|title=Google I/O 2013 - Introduction to Portable Native Client (PNaCl)}}
• {{YouTube|id=2xV_0pTpNj0|title=Google I/O 2009 Native Code for Compute Intensive Web Apps}} – Technical talk at Google I/O 2009
• [https://code.google.com/p/naclports/wiki/PortList A list of OSS projects ported to Native Client]
• [https://chromium.googlesource.com/native_client/src/native_client.git Native Client source code in Git]

Examples

• Folding@home
• [https://gonativeclient.appspot.com/demo PNaCl examples] (runs in Chrome 31+, PNaCl, i.e. no installation needed)
• [https://developer.chrome.com/native-client/sdk/examples Native Client SDK Gallery]
• torapp.info{{dead link|date=October 2017 |bot=InternetArchiveBot |fix-attempted=yes }}, vector editor, especially powerful for security printing (not PNaCl)
• NACLBox, a port of DOSBox to Native Client (PNaCl)
• [https://chrome.google.com/webstore/detail/moehcjggbedbobepfihdamhnlneanioe SodaSynth], a synthesizer for Native Client (not PNaCl)
• [https://pnacl-amiga-emulator.appspot.com/ pnacl-amiga-emulator], a port of UAE, an Amiga 500 emulator
• [https://luzbel.github.io/vigasocosdl-la-abadia-del-crimen.pruebas/ Abadía del crimen], a port of the SDL version of Vigasoco (remake of La Abadía del Crimen) to Native Client (PNaCl)
• Bennugd, a port of Bennugd Videogames examples to Native Client (PNaCl)

• 1987 in baseball
• 1987 in Canada
• 1987 in country music
• 1987 in environment
• 1987 in film
• 1987 in games
• 1987 in Ireland
• 1987 in LGBT rights
• 1987 in literature
• 1987 in music
• 1987 in rail transport
• 1987 in science
• 1987 in Singapore
• 1987 in South Africa
• 1987 in sports
• 1987 in video gaming
• 1987 Irish General Election
• 1987 Irish general election
• 1987 Italian Grand Prix
• 1987 IUSY Festival
• 1987 Japanese Grand Prix
• 1987 Mecca incident
• 1987 Mexican Grand Prix
• 1987 Monaco Grand Prix
• 1987 National League Championship Series