@bkaradzic @chadaustin @TheJare Simpler because closer to existing JIT. Took just a few engineer-months to this point; compare to (P)NaCl.
-
-
Replying to @really_bz
@bz_moz@chadaustin@TheJare I think it's awesome research project, but it will always carry JS abstraction penalty around it's neck.1 reply 0 retweets 0 likes -
Replying to @bkaradzic
@bkaradzic@chadaustin@TheJare The question is what that means in practice. Benchmarks against PNaCl would tell for sure if PNaCl existed.1 reply 0 retweets 0 likes -
Replying to @really_bz
@bz_moz@chadaustin@TheJare It does exist... It's in Pepper 26.1 reply 0 retweets 0 likes -
Replying to @bkaradzic
@bkaradzic@chadaustin@TheJare Interesting. Link, please? How does performance compare to NaCl?2 replies 0 retweets 0 likes -
Replying to @really_bz
@bz_moz@chadaustin@TheJare Actually it's even in Pepper 24 https://developers.google.com/native-client/dev/sdk/release-notes …2 replies 0 retweets 0 likes -
Replying to @bkaradzic
@bkaradzic@chadaustin@TheJare Again, that still involves a static compile+link to particular target architectures.2 replies 0 retweets 0 likes -
Replying to @really_bz
@bz_moz@chadaustin@TheJare Like adding ARM target for mobile is tiny bit of work in comparison of GLES2 work for mobile vs. desktop.2 replies 0 retweets 0 likes -
Replying to @bkaradzic
@bkaradzic@chadaustin@TheJare What matters to me is not how easy it is to port your code, but how easy it is to ship a new hardware arch.1 reply 0 retweets 0 likes -
Replying to @really_bz
@bz_moz@chadaustin@TheJare So you're trying to solve theoretical problems?2 replies 0 retweets 0 likes
@bkaradzic @chadaustin @TheJare If NaCl had shipped in 90s, ARM support would have been "theoretical". I don't want us to fail like that.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.