31–40 of 56 posts
After sadly verifying Microsoft's claims, author goes on to find third party benchmarks where they'd lose to make the point he initially wanted to make.
"Well these tests don't meet my expectations so lets keep testing using other benchmarks until I'm validated".
Honestly, any test between a microsoft product and a competitor run on microsoft's operating system has to be viewed with a grain of salt. What's interesting here is the degree of trust given to a vendor that has tried to rig/break even hardware to lock out competition: http://antitrust.slated.org/www.iowaconsumercase.org/011607/...
And yes, bg still has a lot of swing at microsoft: http://www.businessinsider.com/bill-gates-is-back-at-microso...
Worse below, there are people simultaneously believing in a vendor that has long track record establishing their "rig the game" overarching corporate strategy and dissing the blog author for doubting the vendor's claims, even to the extent of accusing the author, who checked only two HTML5 benchmarks, of going on a witch hunt to find benchmarks that disadvantaged the vendor.
After sadly verifying Microsoft's claims, author goes on to find third party benchmarks where they'd lose to make the point he initially wanted to make.
"Well these tests don't meet my expectations so lets keep testing using other benchmarks until I'm validated".
'It seems like Microsoft has been targeting their optimization effort for the competitor benchmarks in order to show impressive results for their new product. When it comes to more intensive and complex HTML5 benchmarks they are still miles behind the competition.'
Reasonable explanation to me.
Earlier quoted context omitted.
His conclusion stands, he's got 1/2 of the claimed perf gains from the using the benchmarks the Edge Team advertised, but when tested against other Independent benchmarks Edge's performance falls dramatically short, making it reasonable to deduce Edge is optimized around the benchmarks the PR team is advertising.
It's unclear how these additional tests were selected. If the criterium was to find a benchmark where Chrome performs better, then you can't conclude much from this.
Earlier quoted context omitted.
"Well these tests don't meet my expectations so lets keep testing using other benchmarks until I'm validated".
Sounds like FDA approval process.
After sadly verifying Microsoft's claims, author goes on to find third party benchmarks where they'd lose to make the point he initially wanted to make.
Neither of these accusations are in any way constructive. I'd be much more interested in real world examples where one browser or another is noticeably slow.
After sadly verifying Microsoft's claims, author goes on to find third party benchmarks where they'd lose to make the point he initially wanted to make.
The new tests don't seem particularly hand picked given that the are among the top results I get when I google for "Browser speed test", arguably a sign that they aren't overly obscure.
As an aside, all the tests benchmarks are made by parties other than microsoft so they should count as third-party. And their being third party is typically seen as a virtue due to the tendency of vendors overturning on their own benchmarks.
So while this was obviously a bit of hostile benchmarking, it doesn't seem like there was any need for special effort to get a discrediting result, simply benchmarking with other suites proved enough. The fact that the author is clearly hostile to microsoft does not in itself disprove the results presented, and is not ground for dismissing them.
It all depends on your workload. I'm working on a web app that uses typed arrays heavily. Chrome runs my test case in 2.7 seconds, Firefox in 3.2, and IE Edge in 23 seconds... (ie 11 in 30+) Now to be fair i developed "for" firefox, checking that it worked in IE and chrome the whole way, but that is a pretty large performance difference. Plus i've always hated benchmarks. They are so easy to "game" without real impro…
I think you are doing something wrong. I have a light app and very heavy SPA (written really badly with almost 5mb of code, D3 + Highcharts). Still, both app loads in less than 4 seconds in IE 11, FF, Chrome and Safari.
From arewefastyet.com they seem to be doing ok, (even if they keep testing some really slow chrome version for some reason) and so it seems strange they are being left out.