As was said earlier, the Y2K bug was much more plausible.
Put it this way... which of these sounds the MOST plausible, out of these 3 statements?:
- Computers that use a 2-digit year will cease working when the year 2000 hits, as the year will be 00, thus there will be "no" year
- The world will end around the Winter Solstice of 2012, because the "long-count" calender will end.... (just like our calender ends every year <_<)
- Computers will be affected at precisely 3:14:08 UTC on Tuesday, January 19, 2038, when 32-bit Unix Time reaches the maximum, i.e. 10000000 00000000 00000000 00000000, or 2147483647, after which it will wrap around to -2147483648, which is 2,147,483,648 seconds before 00:00:00 UTC on Thursday, January 1, 1970... which is 20:45:52 on Friday, December 13, 1901
A note about #3, is that for the last 5 seconds of 32-bit unix time, and the next 5 seconds after, the Unix time will be:
- 2038-01-19 03:14:03
- 2038-01-19 03:14:04
- 2038-01-19 03:14:05
- 2038-01-19 03:14:06
- 2038-01-19 03:14:07
- 1901-12-13 20:45:52
- 1901-12-13 20:45:53
- 1901-12-13 20:45:54
- 1901-12-13 20:45:55
- 1901-12-13 20:45:56
Just so you know, it is possible to use Unix time, to timestamp quotes... like so:
For example, let's see what happens if I choose 2147483647 (the maximum)
[quote name="NintenDan" timestamp="2147483647"]The timestamp of this quote is the LATEST date/time possible with 32-bit Unix time. 2147483647 is precisely equal to 2[sup]32[/sup] - 1, therefore, one more, is 2[sup]32[/sup][/quote]
On an unrelated note.... can you use negative values?
[quote timestamp="NintenDon timestamp="-1278572987"]OMG! I'm old.... or am I?[/quote]