An important comment on the bug from a Chromium employee [0]
Hacker News crowd, let's please stop the "me too" party
here, and please file separate bugs for separate issues
(even if they're similar). Keeping the signal-to-noise
ratio sane on this one raises the chances that it gets
addressed :)
So you can help by only commenting if you have technical
comments on how to fix the problem in Chrome. It'd be a
shame if we had to lock this bug to prevent further
useless comments.
You can always tell if something is garbage on here by looking at the average length of the comments. Almost every single comment on this link is an inane one-liner that adds nothing to any meaningful discussion. And lo and behold, it's the same sort of shitty discussion as on the bug report itself.
Reminds me of all the +1 comments on GitHub issues. They add nothing to the conversation and you can easily subscribe to an issue by clicking the "watch" button.
Why O(log n)? Is there a binary search involved somewhere (for example)? All you have got to do to find out how many people voted for it is to look at the vote count and this seems like an O(1) operation doesn't it?
