Hacker News new | comments | ask | show | jobs | submit login

I'd like to see Node.js using Chkara by default, V8 developers have showed that they don't care much about Node.js, they are more interested in Chrome, and MS have showed more interest in Node.js than Google and I'm sure it will be better for all, fingers crossed.



I don't. A lot of code out in the wild already relies on v8, and won't work with Chkara. Node 5 is up-to-date with v8. Though, I would like to see Mozilla devsvwpuld revives the unofficial spidermonkey Node.js support (https://news.ycombinator.com/item?id=2469786 , https://github.com/zpao/spidernode ).


This is definitely a problem today, but NAN (https://github.com/nodejs/nan) which is now the recommended way to build native modules, offers a way out. That project provides a stable API to insulate module developers from changes between v8 versions.

Sometime down the line, a NAN-spidermonkey or NAN-chakra project might become feasible.


Sort of -- in practice, we found ourselves instead playing catchup to NAN (many changes across Node 10, 12, 4, etc.). It insulates from minor changes, and increasingly, part of that has been Node waiting longer and longer between v8 changes.


> which is now the recommended way to build native modules, offers a way out

On paper. In reality, HELL NO. I maintain node native addons, and the thing is, NAN is great, but they simply cannot foresee what will break next in v8.

Once something breaks, they provide a node-version-independent feature-shim, but every time there's a new version of Node, I DREAD the work I'm going to have to do to maintain my add ons.

It's simply less work to cross compile C++ to JS w/ Emscripten or write it in JS (or higher level language and compile to JS) in the first place.


>and won't work with Chkara

Is your lost.


I meant many npm modules ;) Not my code. So it would be your problem too.


That's the interesting part, even with V8 updates NPM packages get brocken, I don't see the migration to Chakra as something different to migrating to a newer V8 engine witch also break a lo of stuff.


Not Node.js per se but a separate project that ran on the Chkara core and worked hard for cross-compatibility would be more than welcome.


A node.js fork where you can optionally swap out v8 for chakra: already baked by none other than microsoft.

They hope to merge it back into upstream, that seems possible given the recent history of the Node.js project.

Of course, it is very very unlikely that npm modules with native code work in Node.js/Chakra just yet.


> Of course, it is very very unlikely that npm modules with native code work in Node.js/Chakra just yet.

I would hope they follow the same path as the jxcore+SpiderMonkey team so I don't have to worry about which engine my npm modules support.


Yeah I just seen it on Reddit. Nice job MS.

https://github.com/Microsoft/node


This is the first I've heard that v8 devs don't care for node. Since I am not in the know, are there some sources that detail this issue in depth?




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: