Re:The Future of Node Is in Microsoft’s Fork
by morebetterer on Saturday January 02, 2016 @01:27AM
(#10825330)
It would be very interesting if you could share your team's challenges and insights in creating a Chakra shim that exactly mirrors v8's C++ API so that it's a drop in replacement for v8 for Node. Is it difficult to maintain the Chakra shim against an ever-changing v8 API?
[ Parent
| on HN ]
Re:The Future of Node Is in Microsoft’s Fork
by gauravseth on Saturday January 02, 2016 @01:56AM
(#10825367)
We plan to do a blog post about this when we submit a PR to mainline, but you can see the session at Node Interactive where we discussed some of these - https://www.youtube.com/watch?v=Zbc3SwMDWf0&index=14&list=PL....
Re:The Future of Node Is in Microsoft’s Fork
by morebetterer on Saturday January 02, 2016 @02:49AM
(#10825476)
Good stuff.
Looking forward to the neutral binding layer for different javascript engines for Node.
Ideally for a given platform a native Node module should be ABI compatible with v8 Node or Chakra node - without the need for recompilation.