JavaScript Performance MythBusters (via jsPerf)

Re:JavaScript Performance MythBusters (via jsPerf) by fridek on Saturday March 17, 2012 @09:34AM (#3717025)

Eval breaks both JIT[1] and garbage collection [2] (unless used very carefully). It also affects Google Closure Compiler [3]. What is even better - it won't ever be fixed, at least not in the terms of performance.

[1] http://echo.nextapp.com/site/node/6097

[2] http://stackoverflow.com/questions/5368048/how-are-closures-...

[3] http://groups.google.com/group/closure-compiler-discuss/brow...

[ Parent | on HN ]

Re:JavaScript Performance MythBusters (via jsPerf) by jdd on Saturday March 17, 2012 @03:21PM (#3717921)

Garbage collection was brought up during the Q/A and I would dig a jsPerf revision to explore that.

One of the tests included in the slides was to see if simply using `eval` in a method would disable optimizations: http://jsperf.com/eval-kills

Chris (@robodynamo) included the slide about `eval` because he found it performant/useful in his day job.

Eval has it's uses, for example it's used in json2.js as part of the JSON fallback.

[ Parent | on HN ]