3 ms·
The system I'm working on counts time as an unsigned 32-bit int starting in 1900 (don't ask). I think we fail in 2036 and that's a mere 23 years time. It does
by Graham24 13y ago
The system I'm working on counts time as an unsigned 32-bit int starting in 1900 (don't ask). I think we fail in 2036 and that's a mere 23 years time.
It does really annoy me when idiots talk about the Y2K problem as being nothing at all and just a hyped-up non-event.
I for one, worked on fixes for Y2K and it all went seamlessly because we (collectivly) worked hard and got it right and no reactors/missles blew up and the banks did not fail.
- johansch 13y agoYou might find this thing I found on the web just now amusing: http://forums.buffalotech.com/t5/Storage/CloudStor-Date-Time-02-07-2036-1-28am/td-p/63274 http://forums.buffalotech.com/t5/Storage/CloudStor-Date-Time... "Installed a new CloudStor 2.0TB Pro and no matter what I try on the System...Date/Time settings (manual or automatic), the device date (and ultimately new folder create dates) set themselves back to February 7, 2036 1:28AM. My device timezone is set for UTC-05:00 Eastern Time (US & Canana)."
- glhaynes 13y agoSame thing whenever those "useless" organizations like the World Health Organization monitor/quarantine people and animals showing new strains of the flu. Afterward, I inevitably hear a "well, that sure was a dud... all that expense and trouble over a flu that didn't turn out to be a big deal. They're just trying to scare us to justify their jobs." Infuriating.
- guscost 13y agoWere people actually expecting nuclear reactors to "blow up" because of a software problem? http://en.wikipedia.org/wiki/Passive_nuclear_safety http://en.wikipedia.org/wiki/Passive_nuclear_safety