4 ms·
> If there is functionality that they want which is not standardized, they go ahead and implement it. ... in a non-standardizable way. Why not try to help cre
by a3_nm 9y ago
> If there is functionality that they want which is not standardized, they go ahead and implement it.
... in a non-standardizable way.
Why not try to help create a standard instead? What's the benefit of starting with a dirty approach and deprecating it later?
- indy 9y agoIt's best to have couple of working/competing implementations first before defining a standard.
- hawski 9y agoBecause people prefer something broken now then something good later.
- sangnoir 9y ago> Why not try to help create a standard instead? They do that as well, it's not one or the other. Google had employees working on WebAssembly (along with Mozilla, Apple and Microsoft). Standards take time to be developed and finalized.
- roca 9y agoGoogle had a lot of people working on NaCl and PNaCl for a long time before they started working on WebAssembly.
- sangnoir 9y ago> Google had a lot of people working on NaCl and PNaCl for a long time before they started working on WebAssembly That's probably because NaCl(2011) and PNaCl predate WebAssembly (announced 2015). Google was optimizing Chrome for asm.js as far back as Chrome 28 (July 2013) - less than 5 months after asm.js was announced.