5 ms·
Yep, this was my iPad after I had a broken screen replaced: http://blog.marksmith.org/too-much-security/ http://blog.marksmith.org/too-much-security/ I had to
by mjmsmith 11y ago
Yep, this was my iPad after I had a broken screen replaced: http://blog.marksmith.org/too-much-security/ http://blog.marksmith.org/too-much-security/
I had to reinstall from a backup to enable wifi so it could talk to an ntp server and sort itself out.
- TazeTSchnitzel 11y agoI'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 agoNo 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 agoWhy is that realistic?
- rdancer 11y agoEven if the implementation hurdles raised by others would be overcome, as I am certain they could be, this would help how?
- userbinator 11y ago23510262 minutes from January 1st, 1970 is 2014 September 13, 01:42:00. Matches that date exactly.
- obelisk_ 11y agoYes, they included that in their post below the picture. > NSDate dateWithTimeIntervalSince1970:23510262*60 2014-09-13 13:42:00 +0000 Btw, are they using an Objective C repl?
- jakobegger 11y agoThat might be fscript? http://www.fscript.org http://www.fscript.org
- mjmsmith 11y agoYes, it's F-Script. Playgrounds pre-Swift :)