We are happy to report that as expected, Y2K was a big nothing, not just for ACME Lab's software but all over the world. No doubt the people who spent hundreds of billions of dollars on Y2K compliance feel they deserve the credit. Well, some of them do, for instance the legacy COBOL and RPG programmers. But 99% of that effort was wasted. Feh. Next millennium, just let us programmers do our job.
Here at ACME Labs we have been getting a lot of requests for Y2K Compliance Statements for our freeware. This page is to explain the reasons why we do not issue such statements.
I'm sure we'll think of more reasons as 01jan2000 approaches.
That said, it's unlikely that you'll hit any Y2K problems caused by any code of ours. This is merely because it's all based on Unix or Java, and those systems are inherently resistant to Y2K problems. Both Unix and Java represent dates internally in a homogeneous form, as a count of seconds since an arbitrary "zero moment". In this representation, nothing unusual happens on January 1st 2000, it's just a date like any other.
It's certainly possible to write code with Y2K problems under Unix and Java, but you almost have to do it on purpose. And we didn't.