#10 Really worried about ads, when this is a new evolution in online web content?
The whole point MS and the IE9 team are making is that for HTML5 to work, performance is key. And to accomplish this, they are taking a high level markup set of standards like HTML5 and shoving them to run as close to hardware as possible so you can be viewing CSS/HTML5 content and SVG and yet have it accelerated as close to running on the GPU as possible in this period in browser evolution.
No Flash, Silverlight, WebGL or other technologies needed, run straight HTML5 content and scripts on the hardware and yes even get good performance on a low end machine, so that the HTML5 world is consistent and fast.
This is why MS is urging other Browser makers to move to a hardware level composer so that HTML5 has a chance, because if they don't and web developers can't count on a good FPS in ALL browsers, either HTML5 will fail or IE9 will be the king of HTML5, neither is the optimal situation, even for MS.
#1 Chrome is great at compiling the script and getting the images/content on the screen fast, but beyond that the WebKit heritage fails when it comes to realtime/dynamic rendering of on screen content. Firefox is middle of the road, and Opera is currently the king at doing a reasonable job although they are all still CPU bound, and other than a few multi-core tricks, don't provide the same level of performance of IE9 that does to take HTML5 to running on hardware as close as currently possible.
The flying images demo on a desktop is going to show Chrome choke, and Firefox do maybe ok, and Opera do ok. However, if you go to a low end Netbook, IE9 will still maintain 30fps, where Chrome will choke and even Opera will only get 1-2fps.
|