It’s the same problem, though. “Oh no, we need to store 4 digits instead of 2” vs “Oh no, we need to store int64 instead of int32”. Or y’know, just use RFC3999 if you can’t do 64-bit. It’s a tedious lift, but it’s not a crisis. People that need to change will do.
You might read up on the everlasting prevalence of ancient COBOL still running too much of our banking and government. the same software that caused y2k is still there
The problem is all the existing IoT devices etc that haven’t pre-planned for this. It’s a safe bet a lot of consumer devices with embedded systems haven’t planned for this and likely don’t have user friendly upgrade paths.
I used to work at a major iot company. While, yeah, some devices will probably be left behind, most would’ve had this covered from the outset. The ones left behind were never intended to make it that long anyhow.
It’s the same problem, though. “Oh no, we need to store 4 digits instead of 2” vs “Oh no, we need to store int64 instead of int32”. Or y’know, just use RFC3999 if you can’t do 64-bit. It’s a tedious lift, but it’s not a crisis. People that need to change will do.
You might read up on the everlasting prevalence of ancient COBOL still running too much of our banking and government. the same software that caused y2k is still there
The problem is all the existing IoT devices etc that haven’t pre-planned for this. It’s a safe bet a lot of consumer devices with embedded systems haven’t planned for this and likely don’t have user friendly upgrade paths.
lots of cars too, probably. Its totally not unreasonable for a car to be on the road for 10/15/20 years.
I used to work at a major iot company. While, yeah, some devices will probably be left behind, most would’ve had this covered from the outset. The ones left behind were never intended to make it that long anyhow.