3 ms·
With regards to the HTML5 and CSS3 level standards that Firefox, Chrome and IE10 are going to be supporting by the end of 2012? Yes. Compared to these, the I
by SideburnsOfDoom 15y ago
With regards to the HTML5 and CSS3 level standards that Firefox, Chrome and IE10 are going to be supporting by the end of 2012?
Yes.
Compared to these, the IE8 JavaScript engine is quite slow too.
it's worth looking a few years ahead if IE8 will have another decade of popularity, which isn't impossible. Even without that longevity, the hindrance of the installed base of IE7 and 8 will grow over the next couple of years.
We know what IE10 will have, and roughly when, since it's part of the win8 plans.
- dspillett 15y ago> the IE8 JavaScript engine is quite slow too I would go with very slow. Faster than IE6, but not by nearly as much as more modern browsers are faster than it. DOM manipulation is very slow compared to more modern browsers (recent versions of Chrome, FF, Opera, ..., even IE9) too. DOM changes being slow is what you'll notice more with most code. As an aside: make sure you set X-UA-Compatible (see http://msdn.microsoft.com/en-us/library/cc288325%28VS.85%29.aspx#DCModes http://msdn.microsoft.com/en-us/library/cc288325%28VS.85%29....) otherwise you'll have no idea if people looking at your stuff in IE8 are using compatability mode or not.
- paulirish 15y ago> I would go with _very_ slow. Yup. Here's a chart to put IE6 v IE8 v IE10 javascript engine into perspective: http://goo.gl/3ACqo http://goo.gl/3ACqo
- dspillett 15y agoI'm surprised to see that much difference between IE6 and IE8. Though IIRC the sunspider test is all javascipt processing and no DOM manipulation, so perhaps the fact I pecieve IE8 as not being that much faster may mean that its DOM layer is the bottleneck I'm experiencing. Not unlikely as I don't currently do large amounts of nmuber-crunching and text processing in anything I have to test under IE.