News for hackers. Stuff that matters.
Re:Optimize your Node app by upgrading Node.js by okket on Thursday March 30, 2017 @11:16AM (#13996091)
FYI: Idiomatic Javascript / Builtins should be fast with the recent revamp of the V8 engine (stop writing "CrankScript").

http://benediktmeurer.de/2017/03/01/v8-behind-the-scenes-feb...

https://github.com/v8/v8/wiki/TurboFan

https://www.youtube.com/watch?v=M1FBosB5tjM

Re:Optimize your Node app by upgrading Node.js by ecares on Thursday March 30, 2017 @11:21AM (#13996139)
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.

Re:Optimize your Node app by upgrading Node.js by __s on Thursday March 30, 2017 @07:19PM (#13999802)
Chrome'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/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)