This is awesome, but before anyone uses this for something real keep in mind that the way this works is that Microsoft has created a shim on top of Chakra that exposes a V8 API. If V8 changes its API drastically (which it frequently does) this little experiment is basically over. There is only so much work people can do to keep up with a moving target. Barring NodeJS creating an abstract JS engine API that developers…
Enable Node.js to Run with Microsoft's ChakraCore Engine
61–70 of 130 posts
Re: Enable Node.js to Run with Microsoft's ChakraCore Engine
#62This is awesome, but before anyone uses this for something real keep in mind that the way this works is that Microsoft has created a shim on top of Chakra that exposes a V8 API. If V8 changes its API drastically (which it frequently does) this little experiment is basically over. There is only so much work people can do to keep up with a moving target. Barring NodeJS creating an abstract JS engine API that developers…
Node's and V8's APIs changed so frequently that someone created an abstraction layer called NaN ("Native Abstractions for Node.js") for people developing Node binary plugins. https://github.com/nodejs/nan
Re: Enable Node.js to Run with Microsoft's ChakraCore Engine
#63Earlier quoted context omitted.
The goal is for all of ChakraCore to be broadly cross-platform eventually, including the JIT, and including many more platforms than just Ubuntu x64. The roadmap reflects our next steps for the next 6 months but is not the entire journey. Disclosure: I work on Chakra
>> An implementation of ChakraCore interpreter and runtime, no JIT, on Linux. You should update the wiki if you work on the project then. The stated roadmap goal seems fairly clear and aligns with a typical Microsoft strategy to ensure Windows remains the premium platform for its "open source" efforts. Not being negative that is just the way it has gone in the past so you are fighting an uphill battle. Disclosure: No…
Re: Enable Node.js to Run with Microsoft's ChakraCore Engine
#64This is awesome, but before anyone uses this for something real keep in mind that the way this works is that Microsoft has created a shim on top of Chakra that exposes a V8 API. If V8 changes its API drastically (which it frequently does) this little experiment is basically over. There is only so much work people can do to keep up with a moving target. Barring NodeJS creating an abstract JS engine API that developers…
Node's and V8's APIs changed so frequently that someone created an abstraction layer called NaN ("Native Abstractions for Node.js") for people developing Node binary plugins. https://github.com/nodejs/nan
Re: Enable Node.js to Run with Microsoft's ChakraCore Engine
#65I guess Google has a few conflicts of interest with Go and Dart.
Re: Enable Node.js to Run with Microsoft's ChakraCore Engine
#66What would be cool though, is if we could use vbScript in Node. Because vbScript is even easier to learn then JavaScript!
Re: Enable Node.js to Run with Microsoft's ChakraCore Engine
#67Earlier quoted context omitted.
Yeah, and it's actually really anti-intellectual, since a well adjusted person is capable of both humor-depth and logical-depth understanding among many other things.
I really don't want HN to turn into reddit, with half the thread devoted to jokes/memes, so I appreciate self moderation that discourages that.
Re: Enable Node.js to Run with Microsoft's ChakraCore Engine
#68Why should a developer care about this? What does ChkraCore bring to the table that V8 doesn't ?
ECMAScript 2015 coverage (even some ECMAScript 2016) by ChkraCore is better than V8 (or SpiderMonkey) [1] [1] http://kangax.github.io/compat-table/es6/
Re: Enable Node.js to Run with Microsoft's ChakraCore Engine
#69Re: Enable Node.js to Run with Microsoft's ChakraCore Engine
#70Many posters in that Github Chakra pull request thread appear to be in the "Node is V8 and only V8" camp. This is disappointing. Since when is having a bigger developer community, supporting the latest ES6 standards, and having wider reach for NodeJS a bad thing? Look at what the friendly rivalry has done for the various browsers - the competition benefitted everyone and advanced technology immeasurably.
Edit: even if they had waited until the JITless builds for OS X and Linux were ready I'd be happier. This definitely feels like jumping the gun.