Asm.js is probably the most important moment of JavaScript technology. It allows that JavaScript be used as a high-level assembly language within the browser, providing near native speed. Although limited, Microsoft has joined Mozilla to offer him support.
In fact, the Redmond giant has announced to provide support asm.js library launched by Mozilla in its JavaScript engine Chakra.
See also : HTTP/2: the first HTTP update in 16
Asm.js is not a new language, it's just a JavaScript subset was chosen to allow optimization of compilers, and JavaScript engines in general. The goal is to run much faster than the JavaScript "native". In addition, asm.js is a pure subset of JavaScript and interoperability between platforms and browsers. This means that the engines that offer asm.js holder expose new features, while the engines are not simply have to operate with degraded performance.
The explicit support asm.js was one of the first applications from developers made to Microsoft for it to be included in Internet Explorer. The functionality was promoted to "study" on the status tracker Microsoft last September. It is now "developing".
The main idea behind asm.js is that developers can compile their C / C ++ in this subset of the JavaScript language optimized (using Emscripten compiler) that the browser can then run. Of course, developers could also write their own asm.js compatible code, but it is necessarily the subject of the project. In its current form, the asm.js code runs about 1.5 times slower than the same code C / C ++.
In addition to the announcement that the company has started working on this, Microsoft also said it was working closely with the developers of Firefox for optimization experience with asm.js.
Only Mozilla and Microsoft
Now the real question is why Apple and Google do not see things that way?
The answer to this question is clear enough. Apple will probably not want web applications also bloom faster than native applications, since this could compromise its revenue on the App Store. Google has a system that allows native code run in the sandbox in the browser. This also vis-Ã -vis degree of platform independence through an intermediate language and the JIT compiler. However, Chrome is the only browser that supports it.
Now that Microsoft and Mozilla offer support asm.js, Google could change its position. After all, it is not good for Chrome to be singled out, and that it "works on IE and Firefox."
The question is what will decide the search giant ....
In fact, the Redmond giant has announced to provide support asm.js library launched by Mozilla in its JavaScript engine Chakra.
See also : HTTP/2: the first HTTP update in 16
Asm.js is not a new language, it's just a JavaScript subset was chosen to allow optimization of compilers, and JavaScript engines in general. The goal is to run much faster than the JavaScript "native". In addition, asm.js is a pure subset of JavaScript and interoperability between platforms and browsers. This means that the engines that offer asm.js holder expose new features, while the engines are not simply have to operate with degraded performance.
The explicit support asm.js was one of the first applications from developers made to Microsoft for it to be included in Internet Explorer. The functionality was promoted to "study" on the status tracker Microsoft last September. It is now "developing".
The main idea behind asm.js is that developers can compile their C / C ++ in this subset of the JavaScript language optimized (using Emscripten compiler) that the browser can then run. Of course, developers could also write their own asm.js compatible code, but it is necessarily the subject of the project. In its current form, the asm.js code runs about 1.5 times slower than the same code C / C ++.
In addition to the announcement that the company has started working on this, Microsoft also said it was working closely with the developers of Firefox for optimization experience with asm.js.
Only Mozilla and Microsoft
Now the real question is why Apple and Google do not see things that way?
The answer to this question is clear enough. Apple will probably not want web applications also bloom faster than native applications, since this could compromise its revenue on the App Store. Google has a system that allows native code run in the sandbox in the browser. This also vis-Ã -vis degree of platform independence through an intermediate language and the JIT compiler. However, Chrome is the only browser that supports it.
Now that Microsoft and Mozilla offer support asm.js, Google could change its position. After all, it is not good for Chrome to be singled out, and that it "works on IE and Firefox."
The question is what will decide the search giant ....