Live data from Hacker News

ChakraCore GitHub repository is now open

blogs.windows.com

31–40 of 324 posts

Re: ChakraCore GitHub repository is now open

#31

Even if I'm in danger of stating the obvious, but MS really changed its approach to software. And it is incredibly great having competition in the JS engine market.

> MS really changed its approach to software

Their open-source friendliness has unfortunately coincided with a decline of their respect for user privacy and choice (Windows 10). I find the "New Microsoft" bittersweet.

Re: ChakraCore GitHub repository is now open

#32
post #5

> Finally, you can also use ChakraCore as the JavaScript engine in Node. This is interesting. You can use it as an alternative to v8 for node.js

What is the advantage of this? What does 1 more JS engine buy us?

Independent implementations of standards.

Re: ChakraCore GitHub repository is now open

#34
post #23

Even if I'm in danger of stating the obvious, but MS really changed its approach to software. And it is incredibly great having competition in the JS engine market.

Three existing production-ready open source engines + other embedded options wasn't already "competition"? It's nice to see but, as far as competition within OSS is concerned, it's about 7-8 years too late. MS will no doubt, at some point, release something like Node.js based on this engine. If they do it'll be widely lauded, but you can barely say they're even a "fast follower" here when they're this slow.

Chakra does better than most of its competition on ES6 support: http://kangax.github.io/compat-table/es6/

(I use v8 and javascriptcore all day but I still appreciate it)

Re: ChakraCore GitHub repository is now open

#35
post #29

Good that it's open source, but I found this blurb from their contributing guidelines [0] to be contribution inhibiting: You will need to complete a Contributor License Agreement (CLA) before your pull request can be accepted. This agreement testifies that you are granting us permission to use the source code you are submitting, and that this work is being submitted under appropriate license that we can use it. [0] h…

Most open source projects have a CLA, nowadays. I don't see how this would inhibit contributions.

Re: ChakraCore GitHub repository is now open

#37
post #29

Good that it's open source, but I found this blurb from their contributing guidelines [0] to be contribution inhibiting: You will need to complete a Contributor License Agreement (CLA) before your pull request can be accepted. This agreement testifies that you are granting us permission to use the source code you are submitting, and that this work is being submitted under appropriate license that we can use it. [0] h…

NodeJS has exactly the same restriction.

Re: ChakraCore GitHub repository is now open

#38
post #29

Good that it's open source, but I found this blurb from their contributing guidelines [0] to be contribution inhibiting: You will need to complete a Contributor License Agreement (CLA) before your pull request can be accepted. This agreement testifies that you are granting us permission to use the source code you are submitting, and that this work is being submitted under appropriate license that we can use it. [0] h…

What's wrong with a CLA? It's incredibly common for projects open sourced by companies.

Re: ChakraCore GitHub repository is now open

#39
post #5

> Finally, you can also use ChakraCore as the JavaScript engine in Node. This is interesting. You can use it as an alternative to v8 for node.js

What is the advantage of this? What does 1 more JS engine buy us?

Well, Chakra is a bit ahead of V8 in ES6 implementation right now.

https://kangax.github.io/compat-table/es6/

Re: ChakraCore GitHub repository is now open

#40
post #29

Good that it's open source, but I found this blurb from their contributing guidelines [0] to be contribution inhibiting: You will need to complete a Contributor License Agreement (CLA) before your pull request can be accepted. This agreement testifies that you are granting us permission to use the source code you are submitting, and that this work is being submitted under appropriate license that we can use it. [0] h…

Don't most large organisations require something similar with their own open source projects? I know Google and Facebook do.

It's just a way of confirming that you own the rights to your contribution, and that you explicitly give Microsoft permission to use it. (And if you didn't want to grant them permission, you would have no reason to contribute!)

Post reply on HN