Chakra is still alive and well in IE10, and will be part of the one HTML5 browsing engine that will power both the Metro-Style and Desktop in Windows 8 and Windows RT. (It also will power the version of IE10 that is coming for Windows 7, as far as I know. There have been no publicly-released test builds from the Softies of IE10 for Windows 7 since Platform Preview 2 a year ago, but supposedly this product is still coming.)
According to the latest IEBlog posts, Microsoft has been honing Chakra in some major ways since IE9.
To get these kinds of apps to run even faster, here's what the team said it did:
- Changed "the fundamental approach to generating machine code." According to this week's post, Chakra’s IE10 compiler generates fewer machine instructions for code, "reducing the overall memory footprint and speeding up execution." Apps with floating-point arithmetic, HTML5 games and simulations will be where these changes are most readily noticed.
- Tweaked Chakra's memory allocator and garbage collector. "Chakra now delays the garbage collection at the end of script execution and requests a callback from the browser after an interval of script inactivity," the post explained. The result? The memory footprint shrinks when the browser or one of its tabs becomes inactive. It also means the frequency of garbage collection in animation-driven apps is reduced.
I'm curious to hear what the IE team is doing on the Windows Phone front, going forward. Rumors from earlier this year pointed to the IE Mobile team using a proxy server to deliver pages more quickly in IE10 Mobile on Windows Phone 8 devices. Yes, seemingly like Amazon is doing with Silk....Browser as a service, anyone?