Earlier quoted context omitted.
Sharing only typed arrays shouldn't be hard.
Well it's not sharing, but web workers have a zero-copy way of transferring typed arrays between web workers. [1] It gives many of the benefits of sharing memory without all of the gotchas [1] https://developer.mozilla.org/en-US/docs/Web/API/Transferabl...
Microsoft Edge's JavaScript engine to go open-source
51–60 of 283 posts
Re: Microsoft Edge's JavaScript engine to go open-source
#52Wait, 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...
Yep. They're kicking everyone's asses in ES6 feature coverage. All the more impressive when you consider how they came from behind. http://kangax.github.io/compat-table/es6/ I's almost sad that Edge is not cross-platform.
Re: Microsoft Edge's JavaScript engine to go open-source
#53Wait, 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...
Yep. They're kicking everyone's asses in ES6 feature coverage. All the more impressive when you consider how they came from behind. http://kangax.github.io/compat-table/es6/ I's almost sad that Edge is not cross-platform.
Re: Microsoft Edge's JavaScript engine to go open-source
#54As a mere mortal - How hard would it be for a day programmer to built something cool like an JavaScript engine ? I sometimes have crazy thoughts about the world ending. How hard would it be to built your own javascript engine from scratch ?
BeRo did build a javascript engine from scratch on his own: https://github.com/BeRo1985/besen From the copyright headers he worked on it starting in 2009 and had the first public release in 2014 (actually 2010, see comment below). He certainly worked on other stuff in between too. This is also not a toy implementation. While I have no idea how it compares to state of the art engines, it does feature a whole bunch of…
Re: Microsoft Edge's JavaScript engine to go open-source
#55Earlier quoted context omitted.
Yep. They're kicking everyone's asses in ES6 feature coverage. All the more impressive when you consider how they came from behind. http://kangax.github.io/compat-table/es6/ I's almost sad that Edge is not cross-platform.
Engineer on the Chakra team here. As the blog post says, we are definitely interested in going cross-platform. Which platforms would you be interested in seeing first?
Re: Microsoft Edge's JavaScript engine to go open-source
#56Wait, 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...
Re: Microsoft Edge's JavaScript engine to go open-source
#57Earlier quoted context omitted.
Yep. They're kicking everyone's asses in ES6 feature coverage. All the more impressive when you consider how they came from behind. http://kangax.github.io/compat-table/es6/ I's almost sad that Edge is not cross-platform.
Engineer on the Chakra team here. As the blog post says, we are definitely interested in going cross-platform. Which platforms would you be interested in seeing first?
In all seriousness I'm pretty sure everyone would say POSIX-y systems.
Re: Microsoft Edge's JavaScript engine to go open-source
#58As a mere mortal - How hard would it be for a day programmer to built something cool like an JavaScript engine ? I sometimes have crazy thoughts about the world ending. How hard would it be to built your own javascript engine from scratch ?
Re: Microsoft Edge's JavaScript engine to go open-source
#59Wait, 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.
Re: Microsoft Edge's JavaScript engine to go open-source
#60Earlier quoted context omitted.
Servo is a rendering engine written in Rust, why would it choose Chakra, which is written in C++, over WebKit, which is written in C++?
Servo is use in production by any browser? or any Project like Chakra? or is just an experiment till now?