News for hackers. Stuff that matters.
Re:How every smartphone platform gets the alarm clock wrong by jdbernard on Monday July 14, 2014 @09:15AM (#8030722)
I don't agree that the current way of doing this is "wrong" and that the author's suggestion is "right." Those terms imply objective reasons as to why is one is better, where this is primarily preference, I believe.
Re:How every smartphone platform gets the alarm clock wrong by nemetroid on Monday July 14, 2014 @01:02PM (#8031891)
> As on the Telechron, the “snooze” function on today’s alarm clocks is activated by a larger and easier to press button than the “alarm off” function. Presumably, this design was chosen so that the person being woken (who is probably very drowsy) will be more likely to hit the snooze button (and thus be woken again in several minutes) than the alarm off button (and thus sleep for several extra hours and be really late).

I think that's a compelling argument as any.

Re:How every smartphone platform gets the alarm clock wrong by jdbernard on Monday July 14, 2014 @05:17PM (#8033309)
And yet the top-rated comment is arguing the opposite, frustrated by accidentally hitting the snooze button and then waking their sleeping partner unnecessarily. It's almost like there are multiple differing views, both of which have compelling justifications depending on the preference and circumstances of the user...
Re:How every smartphone platform gets the alarm clock wrong by bhalp1 on Monday July 14, 2014 @10:08AM (#8030956)
Yeah, but the shame is that the author needs to make this bold claim in order to get readership, when the nuances of user experience are not black and white.