https://bugzilla.wikimedia.org/show_bug.cgi?id=58259
--- Comment #5 from Krinkle <[email protected]> --- (In reply to comment #4) > Whether it optimises or not is a separate question, but if globalEval is > affected by either MediaWiki's or jQuery's closure, that'd be an upstream > jQuery bug. Please make sure that is reported upstream (if not already). > So, assuming jQuery did properly scope globalEval, that means V8 has room for optimisation here and do the same thing to globally-scoped eval() as with e.g. new Function. V8 is in a nice healthy and quick iteration through Chrome, so be careful not to optimise for the optimiser, that can and will change. Generally best to optimise for good patterns, and have engines optimise for good code naturally. I'm looking forward to your results from js engines in other browsers. new Function seems like a cleaner and more direct pattern as well, so I'd argue its nicer even if it does not always (yet) perform better. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
