[__jal]

If you were around for the millennium bug, then surely you remember how many people waited until about October, '99 to start looking for problems. If you think those people went looking for another problem 38 years away to fix...

If this class of business is not seeing a problem this minute, it isn't a bug. And it won't be a serious-enough bug to spend money on until whatever workarounds they can think of start having negative effects on income.

Sources: experience with Y2K remediation, experience with small business consulting & software development, experience with humans.

[tormeh]

>experience with humans

So true. That said, thinking 38 years into the future is usually not sensible for most businesses, because it's very possible that they're bankrupt before then. Thinking 21 years into the future also offers poor ROI for the same reason.

[pbhjpbhj]

I was thinking large companies, banks etc.. I'm not in IT/programming but remember (despite being young) that 2 other calendar related 'bugs' were mentioned at the time. IIRC we've had one and the epoch bug is the second.

Strikes me that big businesses would have thought "will we need to do this again in a few years" and acted appropriately and that there should be a trickle down effect as large corps demand future proofing in IT products.

Yes negligence, ignorance, lack of foresight, corner cutting, and other human traits feed in to that.

[tyingq]

Generally, the bigger and older the company is, the more unmaintained cruft you have. Banks would be one of the worst I imagine.