Microsoft Edge's JavaScript engine to go open-source

Post by teh » Sat, Dec 05, 2015, 5:25 PM UTC

jandem wrote: post #109

roddux wrote: post #19

Wait, Edge does better on ES6 coverage than both Chrome and Firefox? Microsoft have seriously stepped up their game, especially seeing as it's now neck and neck for performance with Chrome: http://venturebeat.com/2015/09/10/browser-benchmark-battle-s...

The next Firefox Nightly build should get 84% on that page, much closer to Edge than Firefox 44 (74%). I work on SpiderMonkey and I'm super excited about this news. All JS engines have added more-or-less similar performance optimizations but often implemented differently and I'm really interested to see what the Chakra team did. I'd be happy to write a blog post on it next month, if people are interested.

Post by 0xFFC » Sat, Dec 05, 2015, 5:27 PM UTC

stinos wrote: post #118

0xFFC wrote: post #103

Earlier quoted context omitted.

I think this is perfectly valid point.We can think of it like this, they are pretty competitive and have shitload of resource. but they are not innovative , the moment , they become leader they lose their interest toward growing and growing, although they have huge amount of resource which help them the moment they become underdog. I think this is cultural problem with Microsoft.

but they are not innovative They've had a seperate research department for over 20 years or so, and if memory serves me well quite some innovative things came (and still come) out of there. So I think they is too general in your phrase - there is innovation (also look at recent Surface line etc) but you're right in saying that it doesn't always come out and doesn't make it to the market, probably because the they you…

Post by hackerboos » Sat, Dec 05, 2015, 5:36 PM UTC

aravindet wrote: post #79

hackerboos wrote: post #71

Earlier quoted context omitted.

Not Node.js per se but a separate project that ran on the Chkara core and worked hard for cross-compatibility would be more than welcome.

A node.js fork where you can optionally swap out v8 for chakra: already baked by none other than microsoft. They hope to merge it back into upstream, that seems possible given the recent history of the Node.js project. Of course, it is very very unlikely that npm modules with native code work in Node.js/Chakra just yet.

Post by gsnedders » Sat, Dec 05, 2015, 5:39 PM UTC

Bahamut wrote: post #119

epoch1970 wrote: post #93

Earlier quoted context omitted.

Developers of large JavaScript codebases have come to realize that class-based OO is exactly what they need. Prototype OO sounds interesting in theory, but in practice it tends to not be what's needed. Projects that use it end up trying to poorly imitate class OO. This wouldn't necessarily be a problem, except it isn't done consistently. There are multiple approaches, some of them which don't mesh well with others. C…

Not just that - there are performance implications as well due to browsers being able to use a fixed allocation of memory with classes' properties instead of a dynamically resized amount for objects, which results in less efficient algorithms able to be applied internally for the browser for doing similar operations.

Post by mtgx » Sat, Dec 05, 2015, 5:45 PM UTC

jayflux wrote: post #88

oblio wrote: post #85

Earlier quoted context omitted.

Well, historically, when Microsoft was still in competition-mode, Internet Explorer was kicking Netscape's ass with the later versions. With the first few versions they were playing catch-up, but if I recall correctly, IE 4 and IE 5 actually had more features and better standards compliance than the current Netscape versions, as did IE 6 at its launch. "IE hell" started once Microsoft won the race.

This is very true. Microsoft are at their best when they're the underdog