3 ms·

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

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 improvements in actual code. They are great for development and regression testing, but when used to compare engines i've found they are nearly useless. All that being said, I applaud the IE team for really sticking to their promise of improving the browser and it seems they are going to give Chrome and FF a run for their money soon.

UnoriginalGuy 11y ago
This thread isn't about IE in edge mode it is about the Edge browser shipping with Windows 10 (that replaces IE). IE in edge mode and the Edge browser have different performance characteristics. I'd be interested to see how your test case performs on the Edge browser.
- Klathmon 11y ago
  I meant to refer to their Edge browser (the latest one on the Windows 10 preview). I guess i just have a tendency to throw IE on the front of it. (and i've also been referring to it along with the other IE versions as IE). So the 23 was Edge, and 30+ is IE11 Is the current term for it just "Edge"?
  - UnoriginalGuy 11y ago
    Yes, it is just "Edge." No IE. It is confusing when you add IE because IE 11 has an edge mode (essentially their newest rendering mode). IE 11's edge mode and the Edge browser share a handful of components, but they're selling Edge as a brand new browser with a lot of cruft removed (backwards compatibility) and other improvements which IE won't ever get (11 is the last version).
    - Klathmon 11y ago
      Awesome, I'll remember this. It still pisses me off that they named it that. It's just going to lead to a bunch of annoyance and confusion. IMO something One related would have been nicer, but I'm sure they know what they are doing.
deleted 11y ago
[deleted]
thekingshorses 11y ago
> Chrome runs my test case in 2.7 seconds, Firefox in 3.2, and IE Edge in 23 seconds... (ie 11 in 30+) 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.
- Klathmon 11y ago
  It's not page load, its the actual application running. It does some fairly heavy image manipulation in web workers using typed arrays. The app loads a little faster in IE (the code comes in just under 1mb), but the runtime of my few test cases are magnitudes slower.
- merb 11y ago
  you never did some ng-repeat tables with angularjs .... I do, and the page load for a big table is stunningly way over 10s even on Chrome/FF, while immense on IE11 (never tested EDGE). Of course a simple fix is ReactJS or natively rendering. However due that only 6 Tables are slow and they changed barely we won't fix that, yet.

UnoriginalGuy 11y ago

This thread isn't about IE in edge mode it is about the Edge browser shipping with Windows 10 (that replaces IE). IE in edge mode and the Edge browser have different performance characteristics. I'd be interested to see how your test case performs on the Edge browser.

Klathmon 11y ago
I meant to refer to their Edge browser (the latest one on the Windows 10 preview). I guess i just have a tendency to throw IE on the front of it. (and i've also been referring to it along with the other IE versions as IE). So the 23 was Edge, and 30+ is IE11 Is the current term for it just "Edge"?
- UnoriginalGuy 11y ago
  Yes, it is just "Edge." No IE. It is confusing when you add IE because IE 11 has an edge mode (essentially their newest rendering mode). IE 11's edge mode and the Edge browser share a handful of components, but they're selling Edge as a brand new browser with a lot of cruft removed (backwards compatibility) and other improvements which IE won't ever get (11 is the last version).
  - Klathmon 11y ago
    Awesome, I'll remember this. It still pisses me off that they named it that. It's just going to lead to a bunch of annoyance and confusion. IMO something One related would have been nicer, but I'm sure they know what they are doing.

deleted 11y ago

[deleted]

thekingshorses 11y ago

> Chrome runs my test case in 2.7 seconds, Firefox in 3.2, and IE Edge in 23 seconds... (ie 11 in 30+) 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.

Klathmon 11y ago
It's not page load, its the actual application running. It does some fairly heavy image manipulation in web workers using typed arrays. The app loads a little faster in IE (the code comes in just under 1mb), but the runtime of my few test cases are magnitudes slower.
merb 11y ago
you never did some ng-repeat tables with angularjs .... I do, and the page load for a big table is stunningly way over 10s even on Chrome/FF, while immense on IE11 (never tested EDGE). Of course a simple fix is ReactJS or natively rendering. However due that only 6 Tables are slow and they changed barely we won't fix that, yet.