<story><title>Bringing Asm.js to Chakra and Microsoft Edge</title><url>https://blogs.windows.com/msedgedev/2015/05/07/bringing-asm-js-to-chakra-microsoft-edge/</url></story><parent_chain><item><author>dicroce</author><text>Come on Google! Support asm.js in Chrome.... Give up on Native Client.... Even Microsoft is doing Asm.js now....</text></item></parent_chain><comment><author>tracker1</author><text>Google has done a number of optimizations that enhance asm.js performance while not specifically targeting asm.js.  This results in real time performance that sometimes beats Firefox, which has asm.js built in.  While I would like to see more effort to the areas of asm.js that are slow, I can&amp;#x27;t discount the Chrome&amp;#x2F;v8 team&amp;#x27;s approach.</text></comment>
<story><title>Bringing Asm.js to Chakra and Microsoft Edge</title><url>https://blogs.windows.com/msedgedev/2015/05/07/bringing-asm-js-to-chakra-microsoft-edge/</url></story><parent_chain><item><author>dicroce</author><text>Come on Google! Support asm.js in Chrome.... Give up on Native Client.... Even Microsoft is doing Asm.js now....</text></item></parent_chain><comment><author>flohofwoe</author><text>I would really love to see Native Client on Android as alternative to the dreaded Android NDK, and I really don&amp;#x27;t understand why this hasn&amp;#x27;t already happened, it&amp;#x27;s so incredibly obvious. Just give us the ability to deploy and run a PNaCl executable directly as normal Android application, and without all the Java and JNI shenanigans. The Pepper API has a lot more to offer than what&amp;#x27;s exposed through the NDK headers, and the SDK itself is much easier to get up and running then the NDK.</text></comment>