For what, Firefox is for all practical purposes irrelevant in a Chrome dominated Web, Google can steer WebAssembly into whatever direction fits Chrome.

▲

flohofwoe 2 days ago | parent [-]

That's the situation today, but in 2013 when asm.js was invented Firefox was still relevant.

▲

pjmlp 2 days ago | parent [-]

Yes, and the question in retrospective is was it worth it?

▲

flohofwoe 2 days ago | parent [-]

IMHO: totally. Asm.js developed into WASM, which is better in any aspect than PNaCl (e.g. just one disadvantage is that PNaCl was an ossified subset of LLVM bitcode, this would resulted in the same quagmire that the DX team found themselves in when they based the DXC shader compiler and HLSL bytecode (DXIL) on a snapshot of the LLVM toolchain and bitcode - in the end the only realistic way out for D3D was to switch to a SPIRV flavour).

	▲	pjmlp 2 days ago \| parent [-]
		Yeah but that has nothing to do with bytecode formats, rather the wrong decisions on how to keep up with upstream FOSS projects within commercial entities. Also they would not have such problem, had they used their own MSIL like bytecode instead, like the Phoenix compiler toolchain from MSR that was supposed to eventually replace VC++, in a LLVM like tooling, but ended up being cancelled.