Microsoft Edge's JavaScript engine to go open-source • Hacker News Board

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

#11

Post by nly » Sat, Dec 05, 2015, 3:14 PM UTC

Sir_Cmpwn wrote: post #4

Wow, I'll admit that I haven't been looking at Edge simply because of the IE stigma, but this blog post impressed me. 90% ES6 support? More so than Babel? Awesome. And it's getting open sourced! I hope to see it ported to the Unixes. Perhaps Servo+Chakra could be a thing?

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++?

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

#12

Post by ameen » Sat, Dec 05, 2015, 3:14 PM UTC

sdegutis wrote: post #2

Wow. They're really serious about changing their philosophy aren't they. Using Github for their stuff, making and open sourcing Visual Studio Code, other stuff I can't remember, and now this.

They're aware of the permeance of open-source in current tech scene and want to be a part of it than fight it. Not many startups (except for DreamSpark, BizSpark, and Seattle/Redmond based ones) build on MS stack nowadays. MS audits are dreaded (thanks to Oracle for showing the way) and a diversion for a growing startup. It's better to steer clear of MS & other proprietary tech whilst building a startup.

They're embracing startups since they need them and are changing their business models to cater better to smaller startups than the behemoth enterprises with Office 365, Azure, etc.

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

#13

Post by Klathmon » Sat, Dec 05, 2015, 3:14 PM UTC

miralabs wrote: post #8

I wonder if in the future node will enable swappable js engine edit: ok just found this https://news.ycombinator.com/item?id=9534138

I've hoped for this since it's inception.

It gives the benefits of having multiple competing implementations but unlike the browser platform we (the developers) get to choose which one we use.

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

#14

Post by oblio » Sat, Dec 05, 2015, 3:14 PM UTC

Inthenameofmine wrote: post #6

sdegutis wrote: post #2

Wow. They're really serious about changing their philosophy aren't they. Using Github for their stuff, making and open sourcing Visual Studio Code, other stuff I can't remember, and now this.

If they go full SaaS I would not be surprized if they go Open Source on Windows itself, seriously. I think for that to happen Nadella needs one big win/turnaround and the shareholders might be on board.

Well, it seems feasible if they take out enterprisey features. For example Windows without AD support could be an option. Or without remote desktop support.

The hobbyists would use it as is but no company would touch it without support anyway.

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

#15

Post by eecks » Sat, Dec 05, 2015, 3:15 PM UTC

outside1234 wrote: post #7

sdegutis wrote: post #2

Wow. They're really serious about changing their philosophy aren't they. Using Github for their stuff, making and open sourcing Visual Studio Code, other stuff I can't remember, and now this.

I was literally blown away by Visual Studio Code. It is an amazing editor. I haven't opened sublime since.

I prefer Atom

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

#16

Post by ameen » Sat, Dec 05, 2015, 3:15 PM UTC

outside1234 wrote: post #7

sdegutis wrote: post #2

Wow. They're really serious about changing their philosophy aren't they. Using Github for their stuff, making and open sourcing Visual Studio Code, other stuff I can't remember, and now this.

I was literally blown away by Visual Studio Code. It is an amazing editor. I haven't opened sublime since.

I'm still pretty much on Atom, but yes VSC wasn't expected. I would migrate if most of my plugins were available on there.

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

#17

Post by 1971genocide » Sat, Dec 05, 2015, 3:15 PM UTC

As 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

#18

Post by ameen » Sat, Dec 05, 2015, 3:17 PM UTC

gtirloni wrote: post #3

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 think theoretically Node.js could work without V8, and guess some of MS's work for IoT was indeed that (swapping V8 for Chakra).

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

#19

Post by roddux » Sat, Dec 05, 2015, 3:17 PM UTC

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...

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

#20

Post by Klathmon » Sat, Dec 05, 2015, 3:19 PM UTC

gtirloni wrote: post #3

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'm not sure where the hangup is, but I've found that Edge is fast as hell for initial page startup, but lags behind quite a lot when under heavy load.

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.

[1]https://kangax.github.io/compat-table/es6/