11–20 of 56 posts
> What to make of these results? 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.
Octane and SunSpider give more weight to the rest.
It'd be very impressive if Edge was faster all round.
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.
Issue #1: performance claims based on tests from one device configuration. The best performance data is gathered from as many sources as possible. In the spectrum of statistics, one data point is not enough. Issue #2: "Personally I have found the Peacekeeper results to be a reliable measurement of web browsers performance." Is there data to back up this claim?
TL;DR > What to make of these results? 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.
"Well these tests don't meet my expectations so lets keep testing using other benchmarks until I'm validated".
But the author is upset because it isn't faster for the specific benchmarks he prefers. If it's slower at Peacekeeper does that specifically mean that the browser is now slow ?
And then weirdly Mint/Linux comes into the argument as though it has any relevance to Edge. Nobody is switching operating systems because of browser microbenchmarks.
> For the Edge browser Microsoft has again decided to develop their own rendering engine, instead of relying on open source alternatives (Blink, Gecko, WebKit). I have to doubt their decision as a browser engine is a big development effort and they need to be updating it from now to eternity. Um, why would they move when they already have an engine? Sure you can argue they should have moved to WebKit or Gecko or even…
I sincerely hope they NEVER use another engine. Diversity is our friend, and having multiple engines all on similar terms means that bugs won't end up as "correct" and it helps push everyone forward.
TL;DR > What to make of these results? 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.
As I posted on another comment, the TL;DR is more like this: "Well these tests don't meet my expectations so lets keep testing using other benchmarks until I'm validated".
If Edge can be to Windows 10 what Safari is to OS X, I’ll try to do what I can to move my browser workflow to Edge as much as possible.