4 ms·

Can anyone speak to what sort of impact this might have on NodeJS? Will it be difficult for the project to migrate to that version? Is it expected to break pack

Can anyone speak to what sort of impact this might have on NodeJS? Will it be difficult for the project to migrate to that version? Is it expected to break packages that rely on C bindings?

deleted 10y ago
[deleted]
randiantech 10y ago
Based on what the article says, performance would be improved. Since theres no API changes, it would be safe for NodeJS team to try to upgrade to this new version without regression issues.
- bmeurer 10y ago
  So far the feedback from Node.js users/developers indicates that the --future configuration is a net win. There are some cases where performance degrades, and we are actively working on those. Instructions how to test-drive --future with Node.js can be found here: https://medium.com/@bmeurer/help-us-test-the-future-of-node-js-6079900566f https://medium.com/@bmeurer/help-us-test-the-future-of-node-...
s3th 10y ago
This architecture switch will have no impact on the V8 API. We're working closely with the Node.js team to make sure that this is a smooth transition and early results look as though there are significant performance benefits [0]. Disclaimer: I work on the V8 team. [0]: https://twitter.com/bmeurer/status/834677090381348865 https://twitter.com/bmeurer/status/834677090381348865
- pavs 10y ago
  Probably means I will finally give Atom editor another try. :)
  - ygra 10y ago
    Atom's performance will most likely be more constrained by the algorithms they use than by JS execution speed.
    - sametmax 10y ago
      Since vscode is already pretty fast, you are probably right.