41–50 of 324 posts
Small 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).
> 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?
Earlier 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.
They didn't have a monopoly on spreedsheets or word processors in the early 90s either..
(In case anyone thinks this is more amazing than it is: it runs on Windows only right now. But presumably someone will start working on Unix ports shortly.)
Check out the Linux branch :) we are actively working on a port. Disclaimer: Msft employee on chakra
Earlier quoted context omitted.
Check out the Linux branch :) we are actively working on a port. Disclaimer: Msft employee on chakra
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?
Declaimer: I work for Chakra team.
So... how is it? Do people like Edge's JavaScript support?
* Better ES6 support https://kangax.github.io/compat-table/es6/
* Faster performance http://az648995.vo.msecnd.net/win/2015/12/chakra-performance...
Earlier quoted context omitted.
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)
I'm not disputing MS have made impressive efforts. I've just yet to see anything from them that would make me put long-term stock in their open source commitments.
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.
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?
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.
