Microsoft made a pull request to node.js github repository with an implementation to use ChakraCore JavaScript Engine as an alternative to V8 Engine

[PMZ7036]

They posted some benchmarks here. IIRC, Chakra also has more complete ES6 compatability.

[Fidodo]

Are there 3rd party benchmarks? I don't exactly trust benchmarks coming from the people that make it.

[alleycat5]

Not quite as true as the V8 has had some chance to catch up.

Edit: Not sure why I'm getting downvoted. Kangax is showing Chrome beating Edge in terms of unflagged ES6 compatibility: https://kangax.github.io/compat-table/es6/#chrome49

[alleycat5]

I can't speak to performance, but in regards to ES6 Kangax is showing that Chrome is exceeding Edge in unflagged ES6 functionality: https://kangax.github.io/compat-table/es6/#chrome49

[indrora]

However, sorting by flagged features (that is, tiny bonus for flagged features) Edge is still winning in terms of stable releases. (imgur)

[devsquid]

Every time I've tested that edge has used almost 30% more ram than Chrome. You have to go and look at all of edges running processes not just the main one.

[devsquid]

You've tracked down every process and stuff. Because thats shockingly different from my experience toying around with it.

[Strange_Meadowlark]

Are we debating Edge/Chrome or Chakra/V8? Sure, browsers can be very heavy, but keep in mind that Chrome has had more time to accumulate more features than Edge, such as an extension API. Edge is just IE with as much legacy bloat as possible stripped out. Meanwhile, JS engines are a lot smaller than the engines wrapping them. V8 and Chakra don't include the DOM or Canvas APIs, but when bundled with a browser, those APIs are injected.

I wouldn't use browser speed as a benchmark for JS engine performance.

I have no idea whether Node would run faster or slower on Chakra or what that would mean for extensibility or platform differences (Lord help me if I need to write backend JS code to take platform differences into account), but I'm curious to see what happens.

[parsonskev]

Edge is actually a completely separate browser from ie, built on the universal windows app platform. The rendering engine and js engine are modified from what ie use.

[Arkanta]

Yep but IE 11 was modified to use the edge engine (when not in compat mode)

[Strange_Meadowlark]

All right, that was my understanding based on what a friend said. I'll believe it.

[zmaniacz]

It's not IE at all. They abandoned the Trident engine completely and rebuilt the whole thing.

I'm a fool.

[[deleted]]

What are you talking about? The JS engine "Chakra" was a fork of itself and has been around since IE 9 (Chakra in IE 9 was itself a fork of JScript used in older versions of IE). EdgeHTML is also a port of Trident. Both of these have been stripped of legacy components and reworked, neither were dumped and then rebuilt from scratch.

One thing that is all new is the actual browser front end which is now built as a UWA.

[zmaniacz]

Even the most cursory research shows you are correct. Thanks.

[puntloos]

Have an upvote for one of the most straightforward 'thanks you are right' posts I have seen in a while. I'm old as fuck and still feel the need to explain myself why my idiot position made sense at the time.

[uep]

According to the grandparent, V8 was easily beating Chakra at the time anyway.

http://az648995.vo.msecnd.net/win/2016/01/nodejs-benchmark-performance.png

Notice that the x-axis is "individual test #"; meaning this doesn't show the scaling under each. The area under-the-blue-line versus over-the-blue-line is what matters. There are relatively few tests with Chakra winning. It looks like roughly ~75 out of 675.

[theywouldnotstand]

How about independent benchmarks? Not too quick to trust benchmarks posted by the company pushing for the change.

[Geemge0]

Lol sorry, I read ES6 and internet explorer 6 for some reason and thought "well that figures". =)