Nacl-web-plug-in Portable -
The lessons learned from NaCl’s Software Fault Isolation directly influenced the security design of WebAssembly. Furthermore, the Pepper API pushed the boundaries of what browsers could handle, forcing the development of better web APIs for graphics (WebGL/WebGPU) and multi-threaded processing (Web Workers).
Every time you play a high-end game in your browser or use a complex web-based CAD tool, you are seeing the evolution of the ideas first implemented by the Native Client team. nacl-web-plug-in
Running compiled machine code from untrusted internet sources is inherently dangerous. NaCl solved this by pioneering a strict double-sandbox architecture. 1. Software Fault Isolation (SFI) The lessons learned from NaCl’s Software Fault Isolation
because it is a software component (an extension or browser plugin) rather than a research project. However, the "NACL Web Plug-in" is based on Google's Native Client (NaCl) Software Fault Isolation (SFI) because it is a
Mozilla (Firefox), Apple (Safari), and Microsoft (Edge/IE) refused to implement NaCl. They viewed it as a Google-centric technology that complicated browser architecture.
