I think one big difference is that if right now I play the GL demo on Firefox using asm.js, it works.
If I play the same demo on Chrome.. it works.
Now if I play nacl stuff on ANYTHING else than chrome is does NOT work.
For me its not about having a nice language, it's about being standardized.
Else, I can just provide C binaries, they're faster than nacl anyway.
This is by far the best argument, but how is the performance of asm.js under browsers other than firefox?
Re:Google Introduces Portable Native Client
by vanderZwan on Saturday May 18, 2013 @05:25AM
(#5728347)
> Now if I play nacl stuff on ANYTHING else than chrome is does NOT work.
That's purely an adoption-by-browser problem.
> Else, I can just provide C binaries, they're faster than nacl anyway.
The whole point of both nacl and asm.js was sandboxing.
Re:Google Introduces Portable Native Client
by karlmdavis on Saturday May 18, 2013 @08:07AM
(#5728629)
> That's purely an adoption-by-browser problem.
... which is a pretty big problem, right? Especially since I don't think FF is likely to pick up NaCL unless/until hell freezes over.
We can all make unsubstantiated claims, and not all of us want to use the ghetto that is modern javascript.