4 ms·

I'm surprised the default time/date is UNIX epoch + 0. Realistically, it ought to be the date that version of iOS was released.

• natch 11y ago
  No programmer ever wished for more special cases when integrating date handling code, especially on a networked device and one that's so tightly integrated with other platforms and devices. And imagine the nightmare of testing the device pre-release, all while faking out the dates, both local and on NTP servers and on development desktop machines the under-development devices are tethered to, and somehow knowing exactly when the release day was going to be, possibly years in advance. So... no, I'm not sure about that plan. And I guess the bug would be unaffected in any case.
  • TazeTSchnitzel 11y ago
    > And imagine the nightmare of testing the device pre-release, all while faking out the dates Huh? Why would you set the date to one in the future? Make the date be the one of the build.
• cmrx64 11y ago
  Why is that realistic?
• rdancer 11y ago
  Even if the implementation hurdles raised by others would be overcome, as I am certain they could be, this would help how?
  • ikeboy 11y ago
    Presumably because it would be impossible to set the time back to 1970, avoiding associated issues.
    • rdancer 11y ago
      ... but it wouldn't prevent setting time to 2014. Again, how does this help?