Honestly, I don't see how can we guarantee that the results are going to be accurate since different engines may have crazy optimizations that could invalidate the tests (pre-compilers, delayed evaluation, constants inlining, etc), external factors may be influencing the results as well (browser running for a long time, page refresh / page load, other softwares, etc) and the way that the test is setup may also favor one approach that in different circumstances would behave differently (I've seen it happening before)...
I believe that the best thing is to keep the code "as clean as possible" and just optimize after finding the "real bottleneck" - I've sent this link before but I guess its worth sending it again: http://blog.millermedeiros.com/2010/10/the-performance-dogma/ PS: remind that most apps have way less than 10.000 var statements... sometimes even 10x slower is still fast. -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
