Re:Changing Date to Jan 1, 1970 disables 64-bit iOS devices
by TazeTSchnitzel on Saturday February 13, 2016 @05:58PM
(#11096105)
I'm surprised the default time/date is UNIX epoch + 0. Realistically, it ought to be the date that version of iOS was released.
[ Parent
| on HN ]
Re:Changing Date to Jan 1, 1970 disables 64-bit iOS devices
by natch on Saturday February 13, 2016 @06:22PM
(#11096207)
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.
Re:Changing Date to Jan 1, 1970 disables 64-bit iOS devices
by TazeTSchnitzel on Sunday February 14, 2016 @11:26AM
(#11098843)
> 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.
Re:Changing Date to Jan 1, 1970 disables 64-bit iOS devices
by rdancer on Saturday February 13, 2016 @07:32PM
(#11096456)
Even if the implementation hurdles raised by others would be overcome, as I am certain they could be, this would help how?
Re:Changing Date to Jan 1, 1970 disables 64-bit iOS devices
by ikeboy on Saturday February 13, 2016 @07:35PM
(#11096472)
Presumably because it would be impossible to set the time back to 1970, avoiding associated issues.