I 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?
They are using this API: https://msdn.microsoft.com/en-us/library/dn903710.aspx
Temporary fork enables Node.js to optionally use the Chakra JavaScript engine
11–20 of 104 posts
Re: Temporary fork enables Node.js to optionally use the Chakra JavaScript engine
#12Embrace: https://nodejstools.codeplex.com/ http://azure.microsoft.com/en-us/develop/nodejs/ Extend: https://github.com/Microsoft/node Extinguish: ?
When was the last time they went all the way?
Re: Temporary fork enables Node.js to optionally use the Chakra JavaScript engine
#13Interesting that Microsoft forked Node instead of io.js. The Microsoft repo says, "This branch is 16 commits ahead, 29 commits behind joyent:master".
Re: Temporary fork enables Node.js to optionally use the Chakra JavaScript engine
#14This was a long time coming. I remember some MS folks talking to Ryan Dahl about doing this back at nodeconf 2011.
Re: Temporary fork enables Node.js to optionally use the Chakra JavaScript engine
#15Can 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.
> With every new version of Windows, Explorer gets worse and worse.
This criticism is a bit misplaced here, since the whole reason for this limitation is due to backward compatibility with older versions of Windows (and software written for older versions).
It's not like this is a new change in Windows; it's been there for ages.
Re: Temporary fork enables Node.js to optionally use the Chakra JavaScript engine
#16Will this work on Raspberry Pi?
the chances are good: http://blogs.windows.com/buildingapps/2015/05/12/bringing-no...
Re: Temporary fork enables Node.js to optionally use the Chakra JavaScript engine
#17What about the license of Node.js/Chromium? Isn't linking a closed source library (Chakra) problematic?
You know it includes multiple code parts under various licenses, Wikipedia says: BSD license, MIT License, LGPL, MS-PL and MPL/GPL/LGPL tri-licensed ( http://en.wikipedia.org/wiki/Chromium_(web_browser) )
There is a reason why major open source projects like Linux, etc. choose licenses like GNU GPL v2+. http://en.wikipedia.org/wiki/Embrace,_extend_and_extinguish and http://en.wikipedia.org/wiki/Fear,_uncertainty_and_doubt
Re: Temporary fork enables Node.js to optionally use the Chakra JavaScript engine
#18Embrace: https://nodejstools.codeplex.com/ http://azure.microsoft.com/en-us/develop/nodejs/ Extend: https://github.com/Microsoft/node Extinguish: ?
When was the last time they went all the way?
Re: Temporary fork enables Node.js to optionally use the Chakra JavaScript engine
#19Embrace: https://nodejstools.codeplex.com/ http://azure.microsoft.com/en-us/develop/nodejs/ Extend: https://github.com/Microsoft/node Extinguish: ?
Ugh. You realize there are like 3 people who are still working there who were around when this was really a thing? Yes, Satya was hired in 1992, but he didn't grow up in that culture nor did any of the other current leadership. Most people working there now were in grade school when that was actually a strategy.
Re: Temporary fork enables Node.js to optionally use the Chakra JavaScript engine
#20Can I browse my node_modules folder in Explorer yet? [1] [1] https://github.com/joyent/node/issues/6960
Wow, what's up Microsoft?
Actually, I was thinking, what's up node? Each dependency keeps a private copy of its dependencies? How messed up is that? Or am I just reading that wrong?