3 ms·
You are right, some patterns (like try-catch) have been made optimizable thanks to TurboFan. However: * until ignition is not available by default on Node.js
by ecares 10y ago
You are right, some patterns (like try-catch) have been made optimizable thanks to TurboFan.
However:
* until ignition is not available by default on Node.js (now only through the --ignition flag, or using current master), a lot of these optimization tricks will stay up to date. Also, companies have a history of moving slowly to newer versions of Node.js.
* even with ignition (I just tested it), using Generators (including async functions) is an optimization killer.
- __s 10y agoChrome's generators are still quite fast compared to Firefox. I've currently got a generator stress test in using generators to implement a lua parser: https://github.com/serprex/luwa/blob/2c1ef6be42b804144340a2e8fb79cbfeb4bc9e8a/ast.js https://github.com/serprex/luwa/blob/2c1ef6be42b804144340a2e... Currently trying to rewrite the Exp rule from using combinators to using something that'll properly handle operator precedence (Not keen on having 11 levels of operator precedence encoded in the grammar)