|Support For Asm.js Growing?|
|Written by Ian Elliot|
|Wednesday, 24 September 2014|
You may doubt that the asm.js approach could deliver the performance gains needed, but benchmarks and demos seem to demonstrate that it can. It cannot match tuned native code but for a wide range of graphics and other demanding applications it does run code fast enough to be practical.
Google's attitude to asm.js has to be influenced by its own NaCl approach to getting faster code, but there is no technical reason it can't support both. In the latest experimental compiler TurboFan, which was made public a few days ago, it has been pointed out that there is a new constant:
is this support for special asm.js optimizations? It certainly looks that way, but more digging is needed to find out.
The next crack in the dam is from Microsoft. A few days ago it updated its road map for IE. The majority of "in development" features are *related to ES6 or HTML5 APIs and perfectly reasonable.
One new item in the "Under Consideration" is:
Of course being "Under Consideration" doesn't mean that it will move to "in development" but it is a step in the right direction. There is also the argument that the Microsoft team might have listed it to indicate that they are aware of it or to indicate that they aren't actually against it. The point is that to "support" asm.js they simply have to include one asm.js optimization - which isn't a huge hurdle to get over!
At the moment, things are looking good for asm.js and who knows it might get the support of the big three browsers - Firefox, IE and Chrome - and then Safari would probably follow some time in the distant future. It helps to realize that browsers are not technology driven, but marketing driven.
To be informed about new articles on I Programmer, install the I Programmer Toolbar, subscribe to the RSS feed, follow us on, Twitter, Facebook, Google+ or Linkedin, or sign up for our weekly newsletter.
or email your comment to: email@example.com
|Last Updated ( Wednesday, 24 September 2014 )|