Well, let's agree that IE10 does well whatever it is designed to do well. Cool. Now what? We have an IE10 browser that compares well with Google Chrome, Opera and perhaps Firefox too (I don't know the exact details about your tests that were making Firefox crash as often as you've claimed in your article).
So is this the point where Microsoft takes on the real challenge? Will it go beyond its typical high-speed sales pitch for the new browser and attack the more relevant problem that is to really get those IE6/IE7/IE8 and perhaps even IE9 users to adopt IE10 immediately?
Just a few days ago, I saw on HN how IE6 has become a political election issue in South Korea!
Pushing the lazy and entrenched users out of the hole is a much more important (and harder) problem to solve than to win medals over browser speed and performance tests. Even if tests like these help push the cause of IE10, it would be appropriate to give out all details of the tests and realize why Firefox was 'disagreeing' to your test at all?
So is this the point where Microsoft takes on the real challenge? Will it go beyond its typical high-speed sales pitch for the new browser and attack the more relevant problem that is to really get those IE6/IE7/IE8 and perhaps even IE9 users to adopt IE10 immediately?
Just a few days ago, I saw on HN how IE6 has become a political election issue in South Korea!
Pushing the lazy and entrenched users out of the hole is a much more important (and harder) problem to solve than to win medals over browser speed and performance tests. Even if tests like these help push the cause of IE10, it would be appropriate to give out all details of the tests and realize why Firefox was 'disagreeing' to your test at all?