SoylentNews is people
SoylentNews
http://www.tomshardware.com/news/chrome-deprecates-pnacl-embraces-webassembly,34583.html
Google announced that its Portable Native Client (PNaCl) solution for making native code run inside the browser will be replaced by the new cross-browser web standard called WebAssembly.
Around the same time Google introduced Chrome OS in 2011, it also announced Native Client (NaCl), a sandboxing technology that runs native code inside the browser. This was initially supposed to make Chrome OS a little more useful offline compared to only running web apps that required an internet connection. Two years later, Google also announced PNaCl, which was a more portable version of NaCl that could work on ARM, MIPS, and x86 devices. NaCl, on the other hand, only worked on x86 chips.
Even though Google open sourced PNaCl, as part of the Chromium project, Mozilla ended up creating its own alternative called "asm.js," an optimized subset of JavaScript that could also compile to the assembly language. Mozilla thought that asm.js was far simpler to implement and required no API compatibility, as PNaCl did. As these projects seemed to go nowhere, with everyone promoting their own standard, the major browser vendors seem to have eventually decided on creating WebAssembly.
(Score: 2) by JNCF on Saturday June 03 2017, @05:24PM
In this context, the term "NoScript" [wikipedia.org] is just concerned with the client.
The distinction being drawn is whether or not there is arbitrary logic happening in the browser. You can have an embedded video and still be "just a document," if your video is embedded using a DOM element. If you roll your own video player, that's "more." You can deliver a document with comment boxes and submit buttons, and as long as they're only making requests which redirect the browser the original page is still "just" a document. If there's a client-side script involved in processing the form data it becomes "more."