*The Y2K38 Bug. One wonders if anybody in 2038 will have the chops to deal with this
Conversation
Notices
-
Embed this notice
Bruce Sterling @bruces (bruces@mastodon.social)'s status on Sunday, 20-Apr-2025 07:16:15 JST Bruce Sterling @bruces
-
Embed this notice
Offbeatmammal (offbeatmammal@mastodon.social)'s status on Sunday, 20-Apr-2025 11:27:00 JST Offbeatmammal
@bruces I was very busy in the Y2K run-up (wonder what the COBOL market is like these days?!) so anyone dealing with Y2K38 has my sympathy (especially as the reward for doing a lot of work and minimizing the problem is to be repeatedly told "see, it was no big deal")
-
Embed this notice
Angus McIntyre (angusm@mastodon.social)'s status on Sunday, 20-Apr-2025 17:38:54 JST Angus McIntyre
@bruces In retrospect, the Y2K38 bug was a smaller problem than we feared. The REAL problems started when someone said “Don’t worry, we can use AI to fix this.”
-
Embed this notice