True. But on the other hand, that's the same thing people said about data logging, and then went ahead and used Log4J.
Not to mention that "using code other people wrote to solve complicated problems" means quite a few popular image formats (and a lot of other stuff) uses 32 bit timestamps. Meaning i'll probably just make it to retirement before that particular puppy has a major accident on the IT carpet.
perl -e 'use Crypt::Digest::SHA256 qw[sha256_hex]; print substr(sha256_hex("the Answer To Life, The Universe And Everything"), 6, 2), "\n";'
| [reply]
[d/l] |
Yes, seen as a possible source of income, 't is too bad the Epochalypse doesn't happen earlier. But don't despair, there are some (probably smaller) Bugs still waiting to be slain in the near future ;-)
| [reply] |
Didn't realize the 2k38 problem had a catchy name as well. "Epochalypse". Nice.
With a name like that, this needs a proper Hollywood disaster movie. You know, global catastrophe nearly averted by unlikely (but totally american) hero at the last minute(*), movie ending with U.S. president giving speech before the ruins of the whitehouse...
(*) probably by driving - guns blazing, of course - through all kinds of riots and military blockades to the "worlds time server" in the Rocky Mountains. Fixing the problem by inserting a 5 inch floppy disk(!) into some ancient mainframe with lots of reel-to-reel tapes for extra visual effects.
perl -e 'use Crypt::Digest::SHA256 qw[sha256_hex]; print substr(sha256_hex("the Answer To Life, The Universe And Everything"), 6, 2), "\n";'
| [reply]
[d/l] |
