I am not aware of this problem and am second guessing asking for more information… 😳
Discussion
Mostly concerned with the billions of embedded devices, everything else shouldn’t be too hard.
These devices have no mechanism to push code updates to or hope users will pull appropriate updates in time? Or is your worry just simply too many apps to update, not enough devs?
Most of the devices I worry about dont have a clear path to updating given that it’s a hardware limitation and many of them are more or less permanently deployed. Every esp32 device, for example, will be affected.
K how is this much different from the year 2000 scare that turned out completely uneventful from my standpoint as like, at best a power user or expert? I mean, if some code by then has ossified that long, no dev updates that code and not enough users are support the maintenance of their code… like we don’t know what we don’t know in a lot of respects because we can I hope agree 2038 is still pretty far off so we’re aware of the potential severity of problems with this bug but kinda pretty uncertain still how much anyone should care or direct resources to trying to squash every bug… the original message (year 2000) was hey maybe try and plan your code so if it cares about calendars and such you gotta think about the consequences of that clock rolling over and starting again in the process. 24 years ago already I guarantee you there are 20 year old devs who are writing code might not even have ever heard of Y2K problem.
Plan for success, prepare for the worst in this case obviously which doesn’t really say much except you have the choice which way you direct your energy. You can also direct your thoughts to the “well Y2K had a similar situation, turned out fine. Am I being paranoid now or complacent?” Won’t know until 2038 🤷🏼🍿
Good way of looking at it. I think the major difference between Y2K and now is that the number of embedded devices has exploded since then.