Edge is certainly much faster than Chrome/Firefox for JS processing that I wish I could use it on Linux. Looks like that might be happening. Really great news.
I didn't know Node.js could use anything but v8. This is also very nice.
I didn't know Node.js could use anything but v8. This is also very nice.
I've seen the benchmarks but in my experience it just... lags...
For example, on the kangax ES6 compatibility table [1]. On chrome clicking a column takes less than a second, on Edge (i'm on an up-to-date Windows 10 machine, no preview stuff) it loads faster than in chrome, but takes 3+ seconds to switch between columns.
Even some of the stuff i've written acts similarly, and i can't figure out why.
But for a more "pure" js example, I have an app which does some image processing in the browser using the canvas ImageData stuff and typed arrays.
For whatever reason my test case completes in about 3 seconds in chrome, 3 to 4 seconds in FF, 11 seconds in IE11, and 6 seconds in Edge.
I've profiled the hell out of it and i just can't figure out the reasoning for it, but it's there. (and as a side note, having the dev tools open in Edge obliterates javascript performance, my test case was taking 30+ seconds to run when i had the dev tools open and it took me longer than i'd like to admit to figure that one out)
I have a feeling the problem is that i'm optimizing for V8 because i know it the best, and i'd much rather not do that if possible.
Think about it, Microsoft really wants bing to succeed, for it to happen, Edge has to succeed so I'm sure they are putting their best minds behind it. Its a matter of time.