TLDR/W: Hardware accelerated IE9 HTML5 canvas beats non-hardware accelerated Chrome 6 development HTML5 canvas.
Too Long Didn't Read/Write?
Too long didn't read/watch, I'd guess.
Internet Explorer 9 destroys Chrome 6 in HTML5 speed test (video)
11–20 of 53 posts
Re: Internet Explorer 9 destroys Chrome 6 in HTML5 speed test (video)
#12Earlier quoted context omitted.
It's a good thing that all other browsers have stopped development. Or maybe a better test would be comparing browsers with hardware acceleration against each other? Does anyone compare two games, one with hardware rendering and one with software rendering? No, of course not. That would be crazy.
Chrome is currently the fastest at this; what else would you have them test against?
They can test against whatever they want, but the fact still remains that IE9 is basically using 'specialized hardware' to reach that speed. What happens when Chrome also supports this specialized hardware? [i.e. I hope that the IE Team doesn't feel like they can skimp on performance elsewhere by just throwing hardware at the problem, rather than fixing/improving their engine.]
Re: Internet Explorer 9 destroys Chrome 6 in HTML5 speed test (video)
#13Pretty cool, now we only need to bring hw accel to linux and firefox :). My main browser will allways be a open one since we really shouldnt trust corporations in keeping the we open.
//Anders
Re: Internet Explorer 9 destroys Chrome 6 in HTML5 speed test (video)
#14Earlier quoted context omitted.
It's a good thing that all other browsers have stopped development. Or maybe a better test would be comparing browsers with hardware acceleration against each other? Does anyone compare two games, one with hardware rendering and one with software rendering? No, of course not. That would be crazy.
Chrome is currently the fastest at this; what else would you have them test against?
The current developer build of Chrome/Chromium has hardware acceleration (switch enabled). The 3.7 developer build of Firefox also has it (and it's supposed to be faster than IE9). Why didn't they compare those, since IE9 is also a developer build?
Re: Internet Explorer 9 destroys Chrome 6 in HTML5 speed test (video)
#15Earlier quoted context omitted.
Too Long Didn't Read/Write?
Too long didn't read/watch, I'd guess.
too long didn't really want (?)
Worrying about canvas graphic acceleration without having a standard canvas implementation may be jumping the gun a little, although traditionally that is how HTML has been advanced. Its a case of premature optimization, but then there is potential for payoff in being first to market with a winning strategy...
Re: Internet Explorer 9 destroys Chrome 6 in HTML5 speed test (video)
#16Using hardware acceleration in a contrived example, IE 9 is faster at rendering fish. Yawn. Nothing Microsoft does now can make up how awful IE 6,7, and 8 are and the fact that most of my day-to-day pain is caused by supporting their crap-tastic browsers. Even IE 8 leaks memory like a sieve.
What's frustrating to me is that they could fix the problem of high usage of old IE versions. They just seem to be unwilling to.
They could add in IE7's and IE8's rendering engines into IE9 as compatibility modes, push out IE9 as a forced or automatic update and have HTML5 ready to use in a few weeks. But they seem to be more worried potential whining from update-averse users than holding back the technological progress of the entire internet.
Re: Internet Explorer 9 destroys Chrome 6 in HTML5 speed test (video)
#17I'm disappointed they didn't make a three-way comparison with potatoes.
Re: Internet Explorer 9 destroys Chrome 6 in HTML5 speed test (video)
#18Using hardware acceleration in a contrived example, IE 9 is faster at rendering fish. Yawn. Nothing Microsoft does now can make up how awful IE 6,7, and 8 are and the fact that most of my day-to-day pain is caused by supporting their crap-tastic browsers. Even IE 8 leaks memory like a sieve.
What's frustrating to me is that they could fix the problem of high usage of old IE versions. They just seem to be unwilling to. They could add in IE7's and IE8's rendering engines into IE9 as compatibility modes, push out IE9 as a forced or automatic update and have HTML5 ready to use in a few weeks. But they seem to be more worried potential whining from update-averse users than holding back the technological progr…
Who to piss off: the IT department at almost every major corporation worldwide who pay us billions of dollars a year, or a bunch of bloggers who run Firefox on Macs and would still hate our bones if we cured cancer tomorrow.
Decisions, decisions.
Re: Internet Explorer 9 destroys Chrome 6 in HTML5 speed test (video)
#19Using hardware acceleration in a contrived example, IE 9 is faster at rendering fish. Yawn. Nothing Microsoft does now can make up how awful IE 6,7, and 8 are and the fact that most of my day-to-day pain is caused by supporting their crap-tastic browsers. Even IE 8 leaks memory like a sieve.
What's frustrating to me is that they could fix the problem of high usage of old IE versions. They just seem to be unwilling to. They could add in IE7's and IE8's rendering engines into IE9 as compatibility modes, push out IE9 as a forced or automatic update and have HTML5 ready to use in a few weeks. But they seem to be more worried potential whining from update-averse users than holding back the technological progr…
I forget where I heard it, but in some interview a Microsoft exec claimed no one at MS likes IE6 and they all want to see it die, but that they have signed long running service agreements which basically makes them contractually bound to keep it alive. Now this could all be bullshit, but that appears to be the official line.
Re: Internet Explorer 9 destroys Chrome 6 in HTML5 speed test (video)
#20Using hardware acceleration in a contrived example, IE 9 is faster at rendering fish. Yawn. Nothing Microsoft does now can make up how awful IE 6,7, and 8 are and the fact that most of my day-to-day pain is caused by supporting their crap-tastic browsers. Even IE 8 leaks memory like a sieve.
What's frustrating to me is that they could fix the problem of high usage of old IE versions. They just seem to be unwilling to. They could add in IE7's and IE8's rendering engines into IE9 as compatibility modes, push out IE9 as a forced or automatic update and have HTML5 ready to use in a few weeks. But they seem to be more worried potential whining from update-averse users than holding back the technological progr…
IE9 does have compatibility modes for IE7 and IE8 already (somewhere on the official IE blog there's a flow chart describing how IE decides what rendering mode to use for a given page; it's terrifying)
My understanding is that IE's entire user-base consists of update-averse users these days - everybody who can stomach the idea of changing browsers is already using Chrome or Firefox.