It has just passed the Unix time 1234567890! (or, if you prefer, 0x499602D2, which is not funny at all).
Friday, February 13, 2009 at exactly 23:31:30 (UTC, which I happen to be), is a nice Friday 13th (already spooky).
$ perl -e 'print scalar localtime(1234567890),"\n";'
Fri Feb 13 23:31:30 2009
I suppose you have a Unix at home, of course. Well, you probably do anyway…
Other fancy Unix dates to come:
Next billionth second…
$ perl -e 'print scalar localtime(2000000000),"\n";'
Wed May 18 04:33:20 2033
As far as it can go, with 32bit signed integers…
$ perl -e 'print scalar localtime(0x7FFFFFFF),"\n";'
Tue Jan 19 03:14:07 2038
And some other that passed already:
The first billionth second:
$ perl -e 'print scalar localtime(1000000000),"\n";'
Sun Sep 9 02:46:40 2001
And finally some before the Unix era:
Well, 0xD has the sign bit set, doesn’t it? It’s in the past too…
$ perl -e 'print scalar localtime(0xDEADBEEF),"\n";'
Mon Apr 14 15:27:43 1952
As far as it can go in the past…
$ perl -e 'print scalar localtime(0x80000000),"\n";'
Fri Dec 13 20:45:52 1901
But don’t worry, 64-bit systems can already (and do already) manage times up to 9223372036854775807 seconds back and forth 1st January, 1970. It’s plus and minus 292 million years. It’ll be good to tag even dinosaurs with Unix-time, as well as the Enterprise next-generation.
The only problem is that the two final catastrophes we can’t get rid of: sun becoming a red giant (thus engulfing all planets, or the Milky Way colliding with Andromeda, will happen in no less than 5 billion years from now, which means that we’ll need to change to 128-bit time-stamp eventually.
Happy unix-time 1234567890!!