Very interesting.

I'm surprised that IE 9, which can only run on Microsoft's newest OS, only made it to 95/100 on Acid Test 3, while on my computer (running Vista) Chrome gets to 100/100 flawlessly. Why would they release a "brand new" browser that couldn't keep up with an existing and competing one?

Shitballs upvote.

I'm using FF 4 RC and only got to 96/100 on Acid Test 3.

Horse Porn

Oh, Maddox. I remember finding you in 1999. Now almost all internet traffic is related to social networks! Nerd raaaaaage!

>> ^Skeeve:

Very interesting.
I'm surprised that IE 9, which can only run on Microsoft's newest OS, only made it to 95/100 on Acid Test 3, while on my computer (running Vista) Chrome gets to 100/100 flawlessly. Why would they release a "brand new" browser that couldn't keep up with an existing and competing one?


They did this on purpose. They didn't implement features that aren't finalized and might change in the future to avoid ending up with another IE6 situation where sites/apps made for IE6 don't work in newer browsers because they don't interpret the code the same way the old browser does. In theory a page made for IE9 should work fine in IE11 or Chrome 17 as long as the new browser supports the standard and the features supported by IE9 don't change.

Google uses a different approach and releases new versions supporting all the latest stuff very frequently. The problem with this is that a site that tested fine with for example Chrome 9 will not necessarily work properly in future versions because parts of the standard aren't set in stone and might change.

Wow, great explanation! Thanks!
>> ^DonanFear:

>> ^Skeeve:
Very interesting.
I'm surprised that IE 9, which can only run on Microsoft's newest OS, only made it to 95/100 on Acid Test 3, while on my computer (running Vista) Chrome gets to 100/100 flawlessly. Why would they release a "brand new" browser that couldn't keep up with an existing and competing one?

They did this on purpose. They didn't implement features that aren't finalized and might change in the future to avoid ending up with another IE6 situation where sites/apps made for IE6 don't work in newer browsers because they don't interpret the code the same way the old browser does. In theory a page made for IE9 should work fine in IE11 or Chrome 17 as long as the new browser supports the standard and the features supported by IE9 don't change.
Google uses a different approach and releases new versions supporting all the latest stuff very frequently. The problem with this is that a site that tested fine with for example Chrome 9 will not necessarily work properly in future versions because parts of the standard aren't set in stone and might change.