Re:Issue 224182 - chromium - Chrome wakes me up in the middl...
by denzil_correa on Wednesday March 27, 2013 @07:29AM
(#5448752)
An important comment on the bug from a Chromium employee [0]
[0] https://code.google.com/p/chromium/issues/detail?id=224182#c...
[ Parent
| on HN ]
Re:Issue 224182 - chromium - Chrome wakes me up in the middl...
by h2s on Wednesday March 27, 2013 @07:51AM
(#5448819)
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.
Compare this with the comments on the 21 Nested Callbacks link: https://news.ycombinator.com/item?id=5447287
Re:Issue 224182 - chromium - Chrome wakes me up in the middl...
by gozmike on Wednesday March 27, 2013 @08:05AM
(#5448868)
Agreed. I'd pay for a Chrome extension that would score HN stories by this metric.
Re:Issue 224182 - chromium - Chrome wakes me up in the middl...
by donretag on Wednesday March 27, 2013 @11:00AM
(#5449762)
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.
Re:Issue 224182 - chromium - Chrome wakes me up in the middl...
by rmp2150 on Thursday March 28, 2013 @10:48AM
(#5455077)
Your comment is no better.
Re:Issue 224182 - chromium - Chrome wakes me up in the middl...
by hmottestad on Wednesday March 27, 2013 @07:56AM
(#5448834)
Isn't it nice to know that there really are a bunch of other people who:
1. Have the problem
2. Take the time to voice their wish for a fix
Even the coolest bug will remain unfixed if only one person reports it.
Re:Issue 224182 - chromium - Chrome wakes me up in the middl...
by Jabbles on Wednesday March 27, 2013 @08:08AM
(#5448874)
You can star it. That would tell the developers how many people care about it in O(1) time, without having to wade through O(n) comments.
Alright, O(log n) time.
Re:Issue 224182 - chromium - Chrome wakes me up in the middl...
by rational_indian on Wednesday March 27, 2013 @09:17AM
(#5449178)
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?
Re:Issue 224182 - chromium - Chrome wakes me up in the middl...
by asdfaoeu on Wednesday March 27, 2013 @09:41AM
(#5449294)
The number n has log(n)/log(10) digits so it technically take log(n) time to read it.
Re:Issue 224182 - chromium - Chrome wakes me up in the middl...
by fyi80 on Thursday March 28, 2013 @01:55AM
(#5453489)
only if log(n) > 7. Otherwise, subitization gives constant time reading of the magnitude of n.
Re:Issue 224182 - chromium - Chrome wakes me up in the middl...
by tripzilch on Thursday March 28, 2013 @08:20PM
(#5458519)
Technically, O(log(n) <= 7 ? 1 : log(n)) is still O(log(n)) ... :)
Re:Issue 224182 - chromium - Chrome wakes me up in the middl...
by denzil_correa on Wednesday March 27, 2013 @07:59AM
(#5448843)
> Even the coolest bug will remain unfixed if only one person reports it.
Is that true? The priority of the bug should depend on the properties of the bug and not on the number of bug reporters.