I expected better JS perf, Edge. Disappoint.
-
-
Replying to @codinghorror
@codinghorror I’d be interested to see what the IE11 numbers were on the same machine.1 reply 0 retweets 1 like -
Replying to @jeffkibuule
@jeffkibuule should be worse, why wouldn't it?2 replies 0 retweets 0 likes -
Replying to @codinghorror
@jeffkibuule it is funny I did test this last night and Ember is *identical* in perf on IE11 and Edge. Very sad. Cc:@tomdale@wycats1 reply 0 retweets 0 likes -
Replying to @codinghorror
@codinghorror@jeffkibuule@tomdale are you saying there's something we should be doing to take advantage of Edge better?1 reply 0 retweets 1 like -
Replying to @wycats
@wycats@jeffkibuule@tomdale no, just odd, they did get much higher Kraken and Octane numbers (2x) with Edge but nothing for Ember :(1 reply 0 retweets 0 likes -
Replying to @codinghorror
@codinghorror@jeffkibuule@tomdale safari is still the king of real-world perf.2 replies 9 retweets 10 likes -
Replying to @wycats
@wycats@jeffkibuule@tomdale I think the big difference is that Safari has an Ember test as part of the stuff they optimize for, right?1 reply 0 retweets 0 likes
@codinghorror @jeffkibuule @tomdale yes, but they also just seem to focus more on things that affect real-world perf vs microbenches
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.