Earlier quoted context omitted.
Having more than one engine can mean that there is less of a V8 monoculture. Bugs in V8 don't become "standard" and "things that V8 is really good at" doesn't become "things that Javascript is really good at".
That's what Go does. The reference of the language is [an actual document]( https://golang.org/ref/spec ), not a reference implementation. There are two compilers (gc and gccgo), and this way, no edge-case of an implementation can make its way into programmers' habits, something that tends to happen a lot with JavaScript.
ChakraCore GitHub repository is now open
81–90 of 324 posts
Re: ChakraCore GitHub repository is now open
#82Earlier quoted context omitted.
Aka, Microsoft is again in the "embrace" stage of Embrace, Extend, Extinguish. (Even if its current management has the noblest intentions, who knows how it'll be in two or three years?)
Do you have anything to back this up other than it being your knee-jerk reaction? Microsoft's entire leadership has turned over and it's easy to see that their culture is very different from the days you're talking about. Also, they don't have a monopoly on nearly anything and certainly not on Javascript engines. They couldn't move to the "Extend, Extinguish" phases even if they wanted to.
Yes. They made a 180° turn already. Who says they won't do another?
Customer lock-in isn't Bill Gates' idea. It's a very tempting strategy that you can find virtually everywhere where companies think it'll gain them money.
Re: ChakraCore GitHub repository is now open
#83Good 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…
Yes, many projects do not, but some very popular ones do: Google Go requires one. Apache requires one. Some FSF projects require one. I could go on, but the point is that CLAs exist for good reasons. There may be another, different way to accomplish the same goals, but since it isn't my pocketbook funding the project, I don't feel like I have a right to complain. As such, just because a project has a CLA doesn't mean…
Regardless of what license the project is filed under, as an individual contributor working for free for the community, the license of a project determines the terms under which I am sharing my work. I expect those to be respected in perpetuity, and I would like the right to rescind my contribution if the copyright holder is in violation of the license.
(Please don't turn this into a GPL vs MIT discussion)
EDIT
Echoing other responders here, if you downvoted I would really appreciate the discussion of why.
Re: ChakraCore GitHub repository is now open
#84Even 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
#85Earlier quoted context omitted.
Wouldn't it be far easier with MIT than GPL? The BSD license sure did little to keep the open source roots of Mac OS thriving.
It could help Microsoft close source THEIR implementation later down the line, but it doesn't help them "extinguish" it completely, particularly if third parties wish to maintain it. MIT makes it easy to fork and relatively easy to re-license.
(Companies are able to fork WebKit, and yet it's on a good track to become the new IE6, because Apple doesn't care and their market share force everyone to work around bugs in iOS/OSX Safari.)
Re: ChakraCore GitHub repository is now open
#86Earlier quoted context omitted.
Chakra's not on there yet, but I'd expect it to be soon after this announcement: https://arewefastyet.com
Nor is JavaScriptCore, which has made that website pretty useless to me as of late.
Re: ChakraCore GitHub repository is now open
#87Earlier quoted context omitted.
What is the advantage of this? What does 1 more JS engine buy us?
Competition! Now both teams have one more incentive to innovate and we get better software in the end.
Re: ChakraCore GitHub repository is now open
#88Even 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.
As far as I know they give you the option to opt out of everything. Are they bad even for asking?
Re: ChakraCore GitHub repository is now open
#89Earlier quoted context omitted.
> 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.
While this is true, only open source makes choice and privacy even possible. They are obviously trying to reinvent themselves partly in the image of Google, whose motto "Don't be evil" also sounds very hollow nowadays. But I shudder when I think of a world where Google is built upon closed software. [To clarify: I know that Google does not open most of their software. However, with their reliance on open source softw…
Which makes me agree very hard with your first point, btw.
Re: ChakraCore GitHub repository is now open
#90Earlier quoted context omitted.
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/