Temporary fork enables Node.js to optionally use the Chakra JavaScript engine
1–10 of 104 posts
Re: Temporary fork enables Node.js to optionally use the Chakra JavaScript engine
#2Is there a benchmark comparison available anywhere?
Re: Temporary fork enables Node.js to optionally use the Chakra JavaScript engine
#3Can I browse my node_modules folder in Explorer yet? [1]
Re: Temporary fork enables Node.js to optionally use the Chakra JavaScript engine
#4Will this work on Raspberry Pi?
Re: Temporary fork enables Node.js to optionally use the Chakra JavaScript engine
#5"This temporary fork enables Node.js to optionally use the Chakra JavaScript engine on Windows 10, allowing Node.js to run on Windows on ARM." (the submission title has been updated after I posted this, was initially "MS releases a fork of Node that uses the Chakra JavaScript engine instead of V8")
Looks like they intend to merge back with node mainline... ?
EDIT: Found this: http://blogs.windows.com/buildingapps/2015/05/12/bringing-no...
They're doing this to be able to run Node.js apps on Windows 10 ARM (on which V8 supposedly doesn't run?)
"We will be submitting a pull request to Node.js after stabilizing this code, fixing key gaps and responding to early community feedback."
"Going forward, we plan to work closely with the Node Foundation, the Node.js Technical Committee(s), IO.js contributors and the community to discuss and participate in conversations around creating JavaScript engine agnostic hosting APIs for Node.js, which provide developers a choice of JavaScript engine that they would want to use in their Node.js workflow"
Looks like the pull request will consist mostly of exposing new hooks to integrate with Chakra / other JS engines and won't involve pulling any Chakra code into Node.js (which would be unlikely to be merged). Might lead to a SpiderMonkey version of Node.js at some point, too. Nice to see IO.js mentioned. Looks like a very positive initiative (assuming it doesn't complicate Node core too much)
Re: Temporary fork enables Node.js to optionally use the Chakra JavaScript engine
#6Embrace:
https://nodejstools.codeplex.com/
http://azure.microsoft.com/en-us/develop/nodejs/
Extend: https://github.com/Microsoft/node
Extinguish: ?
Re: Temporary fork enables Node.js to optionally use the Chakra JavaScript engine
#7I wasn't aware that Chakra could be used standalone in this manner. I had assumed that it was tightly bundled to IE. Is this new?
Re: Temporary fork enables Node.js to optionally use the Chakra JavaScript engine
#8Can I browse my node_modules folder in Explorer yet? [1] [1] https://github.com/joyent/node/issues/6960
With every new version of Windows, Explorer gets worse and worse. I personally switched to Directory Opus long time ago.
Re: Temporary fork enables Node.js to optionally use the Chakra JavaScript engine
#9Can I browse my node_modules folder in Explorer yet? [1] [1] https://github.com/joyent/node/issues/6960
Wow, what's up Microsoft?
Re: Temporary fork enables Node.js to optionally use the Chakra JavaScript engine
#10It would be cool if the JavaScript engine was interchangable in NodeJS and IO.JS so you could pick Chakra, V8 or SpiderMonkey very easily. SpiderMonkey is faster than V8 these days on a lot of benchmarks.