Re:History of the browser user-agent string (2008)
by Ajedi32 on Tuesday March 06, 2018 @11:14AM
(#16529724)
Did you read the article I linked? It explains why they went with NaCL over ASM, and why, despite them having a WASM prototype for months now, it's not ready for production yet.
Basically: native threading. NaCL supports it, ASM and WASM don't (yet).
Re:History of the browser user-agent string (2008)
by kuschku on Tuesday March 06, 2018 @11:53AM
(#16530016)
Then don’t release it.
This isn’t the first time Google has released a product exclusively for Chrome, trying to pull more users to their own platform. Even if this is not directly intended, the result is a massive anticompetitive effect.
And despite using a simple compiler backend to compile their native code to NaCl that also allows support for asm.js and WASM in a matter of a few days (entire game engines have been ported that way), Google has been going for months and still kept it Chrome-only.