3 ms·

What does "first class support for node.js" mean in practical terms?

• Klathmon 10y ago
  (This is my interpretation from reading around) They went over it a bit at [0], but the "subtext" is that until recently, Node.js has been "following" what V8 does. When V8 makes a change, node needs to react and work with it. When Node needs to do something differently than chrome, they need to kind of figure it out on their own. Now they are going to be treating node like they treat chrome. Working with them on new features, more integrations with debugging, better support for things that Node.js uses or new APIs to make the Node code simpler. I'm hoping this also means less breakage between Node versions for native code. There's also a (maybe new?) buildbot [1] which is continuously integrating V8 and Node's master branch so you can try out the newest at any time. [0] https://v8project.blogspot.com/2016/12/v8-nodejs.html https://v8project.blogspot.com/2016/12/v8-nodejs.html [1] https://build.chromium.org/p/client.v8.fyi/builders/V8%20-%20node.js%20integration?numbuilds=500 https://build.chromium.org/p/client.v8.fyi/builders/V8%20-%2...
  • Touche 10y ago
    I wonder how much this is related to Node.js cozying up to Chakra and other non-V8 JS engines.