4 ms·
Revision 3 revealed that it's not the `return` that made the difference -- it's the jsperf runner failing to introduce sufficient time gap between testsuites fo
by smilekzs 13y ago
Revision 3 revealed that it's not the `return` that made the difference -- it's the jsperf runner failing to introduce sufficient time gap between testsuites for it to "settle down"...
- deleted 13y ago[deleted]
- eulerphi 13y agoIt's not the jsperf runner, ie. any "settling" of GC sweeping, or anything of that nature. It's surprisingly the location of the DOM elements. See here, I've swapped the two elements, and now the result is _backwards_ http://jsperf.com/always-return-on-jquery-events/21 http://jsperf.com/always-return-on-jquery-events/21 Can anyone with knowledge of the webkit internal DOM id-based key/hashtable shed light on this? I'm guessing that for the 2nd child, when it's propagating upwards, it has to hit 1 more element -- that is, if it must reach the first child to get the parent. I'd hope that the structure is more optimized than a simple crawl to the first node to go upwards. EDIT: Actually, I'm wrong. I edited the test to have 6 divs, and re-arranged the order of the tests. The tests still come in performance-wise from first-to-last, first performing the best. I really don't know what to think now.
- deleted 13y ago[deleted]
- Sidnicious 13y agoeulerphi: FYI you're hellbanned
- Cthulhu_ 13y agoIsn't the idea of hellbanning that people don't realize they are? Kinda defeats the purpose if you notify them of it. If HN wanted people to know they've been silenced, they would be given an error message. So, don't tell people. It's also spamming the comment with offtopic remarks.
- rschmitty 13y agoNot sure what previous action caused him to get hell banned but his comment was trying to contribute something to this thread. Think it would be nice to know if I was banned and still trying to contribute.
- Sidnicious 13y agoSure, that's the idea. The comment looks totally legit and relevant, though. Looks like their last comment sucked, and it's easier for a mod to ban someone than to reply, “that comment sucked” and hope they get better. Mods are never perfect, they have a big job, and people can (successfully) appeal hellbans.
- Dylan16807 13y agoUsing hellbans when you should be using normal bans or even temporary bans is a horrible system. Most people that are hellbanned on HN have not at all deserved it. Ignoring spambots, I've seen perhaps two users that got a hellban for consistently problematic posts rather than a single post annoying someone. And one of those has actual mental issues.
- bicknergseng 13y agoHis interaction with the hn community (and vice versa) is actually one of the most interesting things I've seen on hn.
- badman_ting 13y agoMaybe, but it's pretty obvious when it happens. And of course if that weren't enough, every time you post people tell you that you're hellbanned.
- vidarh 13y agoI browse with showdead on because frankly, apart from the occasional commentspam, pretty much none of the comments I see from hellbanned users are from users who persistently make comments that would seem to justify a ban of any kind. Most of them appear to just have made a single stupid comment at some point or other that perhaps deserved some downvoting. It seems to me that hellbans are overused. And the answer to it being overused is for people to call it out whenever a user is trying to contribute but hellbanned, and we don't agree with the ban after taking a look at their comment history.
- smilekzs 13y agoUh... What happened? Just realized my comment wasn't 100% accurate (it's multiple event listeners rather than unsettled event) but... ?
- Sidnicious 13y agoSorry for the hijacking. Someone named eulerphi replied to your comment, but they're "hellbanned" from Hacker News and their reply is only visible if you turn on showdead in your settings.