4 ms·
pnacl was platform independent llvm bytecode. wasm is something even more wonky.
by andrewchambers 11y ago
pnacl was platform independent llvm bytecode. wasm is something even more wonky.
- michaelwww 11y agoPNaCL was a Chrome only project. According to the announcement, the PNaCL team is teaming up to create a truely multi-vendor solution. "Having both the PNaCl team and the V8 team from Google, along with key people from Microsoft and the asm.js and Emscripten gurus from Mozilla, collaborating closely once everyone saw the light, has been inspiring." https://brendaneich.com/2015/06/from-asm-js-to-webassembly/ https://brendaneich.com/2015/06/from-asm-js-to-webassembly/
- bluejekyll 11y agoHow is this wonky? You want high performing code without the overhead of the compile and dl of the ascii format. JS has done an amazing job up until now, but as more people move their code to client side only, it's becoming clearer that there are better ways to build the web applications. Or maybe this is a non problem, because everything will become native again on the mobile devices. No more html, no more Dom.
- andrewchambers 11y agoIt is wonky because the browser sandbox is a pointless layer between the os and native code. It is just adding more points of failure and bloatING the application stack. Pnacl already did this anyway without reinventing compiler ir in a goofy way.
- bluejekyll 11y agoWasm is basically the evolution of pnacl with backward compatibility through a similar mechanism to asm.js, no? Less wonky and more standard.