This is getting silly. It's fantastic that we finally got canvas in Explorer, but people are putting too much weight to one demo designed to highlight one particularly well performing feature (HW accelerated image draw on canvas #).
This has as much significance as Chrome getting ridiculously better results in V8 benchmark [1] compared to all other browsers.
Please go to CanvasDemos [2] or ChromeExperiments [3] and try some third party canvas demos to see how well IE9 fares across wider variety of canvas use cases.
Spoiler alert: it's nowhere near so clear cut performance champion as it may seem from fish and asteroids demos.
----
Edit: (#) in practical terms, the biggest benefit would go to use cases like the upcoming Aves JS game engine [4] and FreeCiv JS port [5].
I don't think anyone notices Javascript execution performance at this point, but without the hardware acceleration capabilities of Firefox and IE9, HTML5 canvas has no chance of replacing any use-cases of flash.
When the browsers tried to get to 1000 you could see them fluctuating as the os gave and took their resources (even slightly noticeable at 100 (mainly in opera)). They needed to be done one at a time at that point.
On the same computer... at the same time? That seems a little unfair if one browser is choking up the disk access (as Firefox seems to do on me every few seconds).
[+] [-] bd|16 years ago|reply
This has as much significance as Chrome getting ridiculously better results in V8 benchmark [1] compared to all other browsers.
Please go to CanvasDemos [2] or ChromeExperiments [3] and try some third party canvas demos to see how well IE9 fares across wider variety of canvas use cases.
Spoiler alert: it's nowhere near so clear cut performance champion as it may seem from fish and asteroids demos.
----
Edit: (#) in practical terms, the biggest benefit would go to use cases like the upcoming Aves JS game engine [4] and FreeCiv JS port [5].
----
[1] http://v8.googlecode.com/svn/data/benchmarks/current/run.htm...
[2] http://www.canvasdemos.com/
[3] http://www.chromeexperiments.com/
[4] http://www.dextrose.com/en/projects/aves-engine
[5] http://www.freeciv.net/
[+] [-] natmaster|16 years ago|reply
[+] [-] olegk|16 years ago|reply
Sunspider benchmark (Win XP, dual core machine):
Opera (v10.53): 299.8ms +/- 1.0%
Safari (v5): 314.2ms +/- 1.7%
Chrome (v5.0.375.55): 326.6ms +/- 7.9%
Firefox (v3.6.3): 716.4ms +/- 1.7%
[+] [-] CoryMathews|16 years ago|reply
When the browsers tried to get to 1000 you could see them fluctuating as the os gave and took their resources (even slightly noticeable at 100 (mainly in opera)). They needed to be done one at a time at that point.
[+] [-] someone_here|16 years ago|reply
[+] [-] ergo98|16 years ago|reply