On Dec 22, 2:47 am, Shane Tomlinson <[email protected]> wrote: > Balazs, like I said, I already know it is a premature optimization. But, I > still want to know what the reason would be why these discrepancies exist.
To know exactly why you'll need to talk to a browser developer. If you can convince them it's a genuine performance issue, I'm sure they can optimise that part of the engine. But I suspect they aren't concerned. > And to your comment about if I have to perform a loop, then I'm not doing > it right - you don't know what the JS is being used for, nor do I, I am > thinking in a theoretical sense if somebody was using a web worker to > process large data sets, perhaps some sort of image manipulation, and in > that sense, this is a perfectly legitamate question. In this > scenario, perhaps I'm not creating many millions of objects per second, but > I have a couple of objects created that have to call some sort of superclass > function once per operation. Perhaps, but the point being made was that the component of execution time that is attributable to call or apply is insignificant compared to whatever else is being processed, even if one was twice as fast as the other. > Either way, the .call, .apply, etc would still > be used many millions of times. So thanks for the answer, and before > flaming the next person It wasn't a flame. -- Rob -- 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]
