On Thursday, 18 June 2015 at 18:33:16 UTC, Ola Fosheim Grøstad
wrote:
On Thursday, 18 June 2015 at 18:15:32 UTC, weaselcat wrote:
I didn't even read it, I thought it was going to be like a
standardized pnacl from the naming.
Well, it is hard to say what it will become, maybe it is
possible come up with an IR that doesn't sacrifice performance
and still can easily be translated into Javascript with
reasonable performance.
But what's the point? One could compile an application to both
asm.js and WebAssembly instead.
Sounds like politics could turn this into a long stumbling
process.
That is already the case. Mozilla dropped the NaCl wagon in the
middle of the road, letting Google alone on that one, to promote
their concurrent ill advised "standard".
Now there is 2 standard, one that is actually pretty good, but
supported only by google, and another one that is retarded, but
supported more widely. As nobody want to admit they fucked up,
the whole joyous band of over-bloated bogus standard designers
decided to bless us with a 3rd "standard" that is roughly
equivalent to PNaCl, but is not PNaCl, because pride is more
important that webdev's sanity.
