Re:Native equivalents of jQuery functions
by laughinghan on Monday May 20, 2013 @07:28AM
(#5737014)
That has been my experience as well, in fact, I believe the native DocumentFragment code should be slower than the jQuery innerHTML-based code.
[ Parent
| on HN ]
Is not crappy because is slower, is crappy because it destroys all the eventListeners and custom properties of all their childNodes.
Re:Native equivalents of jQuery functions
by brokenparser on Monday May 20, 2013 @08:09AM
(#5737167)
It's crappy because it's not just slow, it manages to freeze Firefox 22 on a 2,8GHz CPU.
At least we agree is crappy. BTW sorry for ruining your perfs, I really wanted to test some few things.
Re:Native equivalents of jQuery functions
by brokenparser on Monday May 20, 2013 @09:09AM
(#5737484)
Okay. Revision 9 adds code to remove the inserted elements, to put every test on equal footing. Is the practical equivalent yours? Because it hits a sweet spot.
The one called "MUCH MORE PRACTIVAL native equivalent" is a mistake, it doesn't do anything. I didn't know documentFragment lacks the innerHTML property so is not doing any parsing like the others.
Re:Native equivalents of jQuery functions
by brokenparser on Monday May 20, 2013 @10:33AM
(#5737877)
Ah, that explains it. I can't submit Firefox results, though. The crappy native equivalent just locks up after throwing several "unresponsive script" warnings.