Advertisement
Don't expect much, as there's no actual browser chrome to enjoy.
And some gratuitous benchmark results...
Discuss this Article 13
oh, so these benchmarks paul buys and doesn't have something snarky to say? god knows he does when apple makes lavish claims like this.
why is he even at this conference, he's an avowed chrome user.
@gfryesc1
Its not just a benchmark chart by itself... you can download and browse with IE9 first-hand, and run the external benchmark from webkit.org yourself.
And who cares if he likes chrome or not, its major news for I.E.
Can't you make this an over 16s only, and get rid of useless comments and tripe such as above, gfryesc1 why come here?
Um. Ok....
I know that software version numbers don't always follow proper decimal rules, but I think it's a typo to put in an extra zero at the end of Opera 10.1 . If there were an Opera 10."ten", I doubt it would be slower than 10.5.
On their website, they actually refer to 10.5 as "10.50", just to clear that up. Or not. ;)
"gfryesc1 why come here"
Cuz he's been banned after trolling Ed's articles on ZDnet.
It'll be interesting to see how much Microsoft improves the engine and such by the time the Beta arrives. Early tech previews kinda present the process, interesting to see how bare bones this creature is.
"I know that software version numbers don't always follow proper decimal rules, but I think it's a typo to put in an extra zero at the end of Opera 10.1 . If there were an Opera 10."ten", I doubt it would be slower than 10.5."
10.1 and 10.10 are the exact same thing. Doesn't matter how many 0's come after. 10.5 would still come after 10.10000000, so it does indeed follow proper decimal rules.
"10.1 and 10.10 are the exact same thing. Doesn't matter how many 0's come after. 10.5 would still come after 10.10000000, so it does indeed follow proper decimal rules."
Sometimes with software revisions, that's not always true.
Some software revisions are shown as a decimal, when it's the build number that changes, not the whole number. ie. v.100.95 is lower than 100.126, because the ".126" is an expression of "build 126", which would be lower than "build 95", even though it wouldn't be expressed that way in purely mathematical figures. It's all in the way that the developer expresses different number sets and there are numerous examples of this.
Also, sometimes developers will just synthetically use lower numbers that look better on paper. Microsoft has even done this with beta forking.
IE8 really that slow? I knew it sucked, but that much even scares me.
I find it amusing using the IE9 preview without any real UI to navigate with. I do hope Microsoft does some good with it and pass the full Acid3 test.
@Logjamming
What's your picture about? It's quite difficult to see
I tried out these demos on my iphone.
Most of them worked just fine, although some of the graphic intensive ones were pretty slow. 1 fps on flying images and the falling balls was pretty slow as well.
Text scrolling & css were very snappy and even the map zoom was usable.
17640ms fir Sunspider though :(
