Where can I find side-by-side benchmarks for Chakra, JavaScriptCore and V8?
Chakra's not on there yet, but I'd expect it to be soon after this announcement: https://arewefastyet.com
ChakraCore GitHub repository is now open
61–70 of 324 posts
Re: ChakraCore GitHub repository is now open
#62Earlier quoted context omitted.
What is the advantage of this? What does 1 more JS engine buy us?
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.
Re: ChakraCore GitHub repository is now open
#63Good 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 there's anything nefarious or inhibiting going on.
Re: ChakraCore GitHub repository is now open
#64Earlier 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.
Even at the MOST EVIL Time of Microsoft some parts of Microsoft were very PRO Open Source even while they said "Linux is Cancer."
Big Corporations can have mixed messages. Apple (My most hated company in Tech has also been very good to Open Source with some projects)
Re: ChakraCore GitHub repository is now open
#65> 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
Microsoft is already working on lighting Node.js with ChakraCore.
Re: ChakraCore GitHub repository is now open
#66Small thing, but nice to see that the API is exposed as C (easy to write bindings for) instead of C++ (near-impossible to write bindings for).
Slight derail but I find it interesting that the Swift team is tackling the fragile ABI problem with v3... Something C++ could have done at any time, enabling portable and interoperable C++ interfaces. (There's no reason clang importer couldn't surface C++ or any other language to Swift for that matter)
Yeah. As much as I absolutely love C++11, and use its features constantly, if I had to make the hard call: "do I get lambdas, or do I get some extern ABI marker I can use to opt-in to a non-fragile ABI, with field and vtable offsets linked as symbols and return types mangled into function names", I would have made the (incredibly depressing) choice for the latter, as it makes C++ suddenly able to be used in ways that are otherwise insane to contemplate.
Re: ChakraCore GitHub repository is now open
#67> ChakraCore
> The MIT License (MIT)
> Copyright (c) Microsoft Corporation
Incredible!
https://github.com/Microsoft/ChakraCore/blob/master/LICENSE....
Re: ChakraCore GitHub repository is now open
#68Earlier quoted context omitted.
Check out the Linux branch :) we are actively working on a port. Disclaimer: Msft employee on chakra
Why port rather than just writing it to be portable from the start? Seems like a lot of work?
Chakra was originally written for Internet Explorer 9. "Linux compatibility" was not exactly a huge priority at Microsoft at the time.
Re: ChakraCore GitHub repository is now open
#69Earlier quoted context omitted.
From the Roadmap document - it seems like JIT on Linux is not a priority? That's surprising. Is it due to technical issues or the whole idea is to have NodeJS on Windows use Chakra and let the community do the Linux part with JIT?
The first step is to get the runtime and interpreter running. Next step is to bring the jit up. Chakra is the hybrid engine where we have the interpreter, simple jit and full jit. The interpreter is the one which does all the profile data collection. Profile data is required to get the quality jit code. Declaimer: I work for Chakra team.
That sounds better - you may want to consider updating the Roadmap document to clarify this.
Re: ChakraCore GitHub repository is now open
#70Earlier quoted context omitted.
What's wrong with a CLA? It's incredibly common for projects open sourced by companies.
It means that the company owns the copyright to everything and can close the source again any time they want. EDIT Dear mods. Some pretty measured posts are getting serious heat in this (and other threads relating to MS) maybe you could look into it?
Many license allows that without a CLA. The CLA allows the company to change the license of the code to whatever they want. Which is usually inhibited by license compatibility...