Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Microsoft Edge's JavaScript engine to go open-source

blogs.windows.com

Post reply on HN
Print view View original

131–140 of 283 posts

Re: Microsoft Edge's JavaScript engine to go open-source

#131

Post by pmelendez »

inglor wrote: post #116
pmelendez wrote: post #97

Earlier quoted context omitted.

I would be very insteresting to see a Chakra-based Node.js project for server side apps, so Linux would be my first vote :)

Microsoft is already working on Node, and it's actually already possible to run Node on Chakra. See https://blogs.windows.com/buildingapps/2015/05/12/bringing-n... and https://ms-iot.github.io/content/en-US/win10/samples/Nodejs....

That's cool but only run on Windows 10 which limit its usage and hence the community. A widely used non-V8 Node.js would be a great project in my opinion.

Re: Microsoft Edge's JavaScript engine to go open-source

#132

Post by eiopa »

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.

Super interested!

Re: Microsoft Edge's JavaScript engine to go open-source

#133

Post by oblio »

Stratoscope wrote: post #122
0xFFC wrote: post #114

Earlier quoted context omitted.

>And luckily for US I am having hard time understanding why luckily for US ? Disclaimer : I am not US citizen nor inside us.

I think the parent comment meant "us" like "you and me," not the USA. The capital letters were just for emphasis.

It was actually a typo, but you're right that I wanted to emphasize that aspect.

Freudian slip :)

Re: Microsoft Edge's JavaScript engine to go open-source

#134

Post by auvrw »

inglor wrote: post #116
pmelendez wrote: post #97

Earlier quoted context omitted.

I would be very insteresting to see a Chakra-based Node.js project for server side apps, so Linux would be my first vote :)

Microsoft is already working on Node, and it's actually already possible to run Node on Chakra. See https://blogs.windows.com/buildingapps/2015/05/12/bringing-n... and https://ms-iot.github.io/content/en-US/win10/samples/Nodejs....

and circumstantially express (?)

https://github.com/ericf/express-handlebars/pull/141#issueco...

Re: Microsoft Edge's JavaScript engine to go open-source

#135

Post by spicyj »

gsnedders wrote: post #128
spicyj wrote: post #106

Earlier quoted context omitted.

They've already built it, I think before V8 existed or around the same timeframe.

It was years later. V8 shipped in 2008, having been in development for (IIRC) three years. Chakra got its first public preview release in 2010, and shipped in 2011—I strongly suspect it started after V8 first shipped.

Thanks for the correction.

Re: Microsoft Edge's JavaScript engine to go open-source

#136

Post by stupidcar »

arnold_palmur wrote: post #46
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...

I wonder if Microsoft is actually spearheading the implementation of ES6 in the browser or did they benefit from the timelines of the ES6 specification fortuitously lining up with the development of Edge - or maybe both.

Not sure what you mean by "lining up with"? The development of ES6/ES2015, and the development of all the browsers and their various JS engines are pretty much ongoing, all the time.

The Edge, Chrome, Firefox and WebKit teams are all working on ES6 compatibility, and releasing new versions pretty frequently. The Edge team are in the lead because they've implemented more features, faster.

Chrome/V8 was actually quite a way behind for a while, although they've caught up quite a bit recently. I believe the situation wrt to V8 within Google was a bit messy for a while, as the original developers (Lars Bak, etc.) were more interested in championing Dart than implementing the latest ES6 features. Eventually, Google had to create a new team, based in Munich, to work on V8.

Re: Microsoft Edge's JavaScript engine to go open-source

#138

Post by Manishearth »

seba_dos1 wrote: post #87
Manishearth wrote: post #77

Earlier quoted context omitted.

You're comparing apples and oranges here. Rendering engines (all in C++ except Servo): - Servo - Blink (Chrome/Opera) - Trident/Spartan (IE/Edge) - Webkit (Safari) JS engines: - Spidermonkey (used by Servo and Firefox) - Chakra (used by Trident/Edge) - V8 (used by Blink, also by Node) Servo already uses a JS engine in C++ because a Rust JS engine is a huge undertaking in itself (see [1]) It does make sense to try out…

Webkit uses JavaScriptCore, not V8.

TIL; fixed, thanks.

Re: Microsoft Edge's JavaScript engine to go open-source

#140

Post by Manishearth »

hiteshk_msft wrote: post #82
Manishearth wrote: post #73

Earlier quoted context omitted.

> Perhaps Servo+Chakra could be a thing? Sounds like a lot of work (not to say it's not possible or interesting). Our bindings code[1] is pretty complicated already. It depends highly on how Chakra deals with things internally -- if it's similar to SpiderMonkey; I'd be interested in having a look. Might become a fun project :) Without a reference open source DOM implementation (which we have for SM -- Firefox's DOM),…

Engineer on Chakra here- are these the docs you're looking for? https://msdn.microsoft.com/en-us/library/dn249552(v=vs.94).a...

Yep! Especially the reference.

Will have a look and compare with the spidermonkey bindings when I get time.

Thanks!

Post reply on HN