Thanks Sanford,
OK i'am using your code:
complain.erase(element.get('id').toInt());
it looks much better and when it's faster :)I agree to Oskar it's will be quite good to have more informations about speeding up. On 16 Apr., 22:55, "Matthew Hazlett" <[email protected]> wrote: > I'd appreciate seeing any performance data/findings you have to share, I > often don't go to that level because most of the JS I do is for small > projects where saving the user a few milliseconds is not going to increase > efficiency in any meaningful way. > > But I would definitely like to focus on this more then I have. > > > > -----Original Message----- > From: [email protected] > > [mailto:[email protected]] On Behalf Of Sanford Whiteman > Sent: Friday, April 16, 2010 4:20 PM > To: Oskar Krawczyk > Subject: Re: [Moo] Re: cant erase element why not? > > > Interesting. Thanks for sharing this Sandy. I wish there was more > > blog posts out there focusing on JS performance - I'm a bit shaky in > > this specific area. > > Yeah, often the performance diffs are negligible or take too many > iterations to show up, but it's something I'm always interested in. > > This one is so glaring that it's hard to ignore. Actually, even in > Safari, unary+ blows away parseInt() (though all the numbers there are > too-small-to-care). > > (Maybe I shall blog about this stuff... but everyone says that.) > > -- S. > > -- > Subscription > settings:http://groups.google.com/group/mootools-users/subscribe?hl=en- > Zitierten Text ausblenden - > > - Zitierten Text anzeigen -
