The linked site shows that performance of eval and new Function are dramatically slower (in the order of 2x slower) than eval and new Function in other browsers. We should investigate why this is the case.
new Function (at least) results in a double parse -- eg. new Function(string) is considered function /*foo*/ (..) { string } which parses the function statement, but does not generate an AST for `string` as it is inside the function statement
We could eagerly build the function, but we need to weigh the costs and benefits of doing so.
Retested JSC performance for eval/new Function is 67/389, V8 performance is 82/84, Firefox performance is 71/456. We're faster than firefox, and only slower now on new Function. Updating title accordingly.