Mozilla can produce near-native performance on the Web

Re:Mozilla can produce near-native performance on the Web by npalli on Thursday May 23, 2013 @12:02AM (#5755288)

Ok thanks. I guess I'm confused about the gains with asm.js. Looks like it is in the same ballpark performance wise as regular JS (and slower in some cases). So, why would anyone write in a crippled C-like subset of javascript and get normal javascript like performance. In the future if threading and SIMD is standardized, won't regular JS gain performance as well?

[ Parent | on HN ]

Re:Mozilla can produce near-native performance on the Web by azakai on Thursday May 23, 2013 @12:05AM (#5755294)

No, look again at the numbers - asm.js gets much closer to native speed than normal JS, in many cases, especially large apps. In addition to the numbers in the article, you can see for example,

http://kripken.github.io/mloc_emscripten_talk/#/28

asm.js code makes it easier to get within reach of native performance.

[ Parent | on HN ]

Re:Mozilla can produce near-native performance on the Web by bad_user on Thursday May 23, 2013 @03:35AM (#5755720)

> why would anyone write in a crippled C-like subset of javascript

Because asm.js is not meant for people, but for compilers.

For example the Unreal Engine has been recently compiled from C/C++ to asm.js and is running in the browser: http://www.unrealengine.com/html5/

[ Parent | on HN ]

Re:Mozilla can produce near-native performance on the Web by camus on Thursday May 23, 2013 @09:32AM (#5756709)

... best viewed in ... netscape ?

[ Parent | on HN ]

Re:Mozilla can produce near-native performance on the Web by cristiantincu on Thursday May 23, 2013 @01:54PM (#5758286)

“Best viewed in Netscape” still wins over “Download for Windows (x86)”.

[ Parent | on HN ]

Re:Mozilla can produce near-native performance on the Web by riffraff on Thursday May 23, 2013 @03:50AM (#5755750)

you are not expected to write asm.js, it's to be considered a compiler target (for e.g. emscripten etc)

[ Parent | on HN ]