Ask Different is a question and answer site for power users of Apple hardware and software. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Just pure curiosity! Last year, the bug is fixed on Jan 2nd too. Both are those days are Monday. Is this just coincidence?

What kind of programming mistake that lead to this bug?

share|improve this question

closed as off topic by patrix, Mark, bassplayer7, bmike Jan 3 '13 at 15:10

Questions on Ask Different are expected to relate to Apple hardware or software within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

Of what I read, it's because next week starts on monday 7 and the current week is sharerd on 2012 and 2013 but still considered as week 1 on calendars. – Matthieu Riegler Jan 3 '13 at 10:58
this is so so lame, how much cash have apple got and they can't fix a bug any script kiddy could – NimChimpsky Jan 3 '13 at 12:34
I would really like to know an 'official' answer to this too – Andy Jan 3 '13 at 13:46
Speculation about why Apple did something is off-topic here. Questions about how to work around a bug or the user-end points of a bug are on topic here and pretty well documented by Apple as well. You might see about asking on Stack Overflow if you have date code that is buggy or Programmers if you want to discuss what class of code is susceptible to bugs of this nature, but we don't host programming questions here. – bmike Jan 3 '13 at 15:19

Browse other questions tagged or ask your own question.