Read more.Quote:
App gave some users an unwelcome lie-in.
Printable View
Read more.Quote:
App gave some users an unwelcome lie-in.
Lucky for Apple it was over a time when most people didn't need to be up for work. They're starting to slip up, tbh.
*clears throat*
...
HA-HA!!
So... all Apple said was "It's your own fault for not setting a recuring alarm". Smooth
I made my own binary LED alarm clock, I accidentally got the maths a tiny bit wrong, I noticed when I was running it in the emulator, this was well before I even had started using unit testing!
But then again every time I use Apple stuff I think they spent the QA budget on advertising. Because people tell you explicitly (without knowing what your doing) that its 'better' then when you say what you want to do, your looked at like a freak. "Oh pentax sir, well then you need to upgrade to the latest version of the OS to use that file format".......
But an ex aside who always insisted on buying apple, I mean her wealthy parents buying it for her, until 6 months after I stopped seeing her and she saw the light, might leave me a bit bitter.... But this is just funny.
You'd think out of all the parts of an OS, the clock would be the simplest to get right after a calculator...
You also have to wonder if this problem will ever go away, because not everyone keeps their product up to date and I'll also bet that come the spring it still won't be fixed on all devices
In fairness though, that only becomes a problem if there are other alarm bugs that these users might run into. I don't know why the alarm stopped working for the last couple of days, but if it is something unique about the 1st and 2nd of January 2011, there isn't going to be another problem.Quote:
Originally Posted by Lucio
Unlike the DST bug from a few months ago, this now doesn't need fixed as the problem has now gone away.
Again the masses fail at using Apple and its obvious God hasn't gave them the gift of correctly using Apple devices. Just like when the people didn't hold their iPhone 4 right when making calls :)
Or so Apple would say . . . . . But I guess they can't just come out and say Iphone sucks buy an ACTUAL alarm clock :P
It's just more bloated code and temporal math fail. If they were doing it right, the 1st & 2nd of January would be no more or less special than any other point in time. And why reoccurring alarms should be triggered in a separate manner from 'one-off' alarms is beyond me entirely.
The bigger issue IMO is that this bug and the DST bug earlier in the year was known before the event, but apple didn't act either to pre-announce or release a fix.
They prefer the head in the sand approach.
Anyone explain this bug ? and why it only affects the first 3 days of a year?
[edit] it seems to be to do with the fact that its the last "week" of 2010 until the 3rd, which is the first week of 2011.
1. Reinventing the wheel
2. Probably got interns doing boring/uncool code like this
3. Non-existent QA
4. Generally inferior OS.
Good thing i chose Android then.. i always get up on time.
Why uses alarm on the phone? Get a real clock with alarm people...
If you rely on software to wake you up then you are late! :P
I don't use my phone's alarm to wake me, but I do use it to remind me of various things, for example doing break duty at work... though I do use it if I'm on the road, say staying in a hotel.
Thankfully I got a phone which works.
Because its easier (always with me, where ever i am travelling/staying) and because "it just works" :)Quote:
Originally Posted by spoon_
'real clocks' use software as well. It just tends to be less ****ty than Crappleware.Quote:
Originally Posted by spoon_