Earlier quoted context omitted.
> Mozilla invented asm.js, an open, backwards-compatible and fascinating alternative to Google's proprietary Chrome-only Native Client technology. Native Client isn't proprietary, its open -- no other browser vendor has adopted it, but that doesn't change the fact that its open. Backward compatible is a real issue with asm.js vs. NaCl, there is no reason to obscure the real issue by throwing a fake one in with it.
Oh, fair dos. But I think asm.js is so much of a better idea that there's no reason to support NaCl - asm.js does everything it's supposed to do but better. I think it was a pretty nice move from Mozilla.
A key focus of NaCl and asm.js is performance, and IIRC most benchmarks are showing NaCl with somewhere between a 25%-33% additional overhead over native C, and asm.js with somewhere in the neighborhood of 100% additional overhead, so I don't think I can quite agree that asm.js does everything NaCl is supposed to do but better.
That said, the other advantages are there, and the performance gap may close.