4 ms·
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 eve
by fridek 15y ago
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 http://echo.nextapp.com/site/node/6097
[2] http://stackoverflow.com/questions/5368048/how-are-closures-and-scopes-represented-at-run-time-in-javascript http://stackoverflow.com/questions/5368048/how-are-closures-...
[3] http://groups.google.com/group/closure-compiler-discuss/browse_thread/thread/e01e087142784940/4e4dd45ee97fc1c8 http://groups.google.com/group/closure-compiler-discuss/brow...
- jdd 15y agoGarbage 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 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.