[onion2k]

I'm less confident than you, because the perceived value of software has dropped considerably over the past 20 years. In the 1970s through to the 1990s when a business bought some custom code it was treated like an asset. It had value. That's one reason why Y2K wasn't a disaster - companies wanted to protect their asset and keep it working.

Today software is cheap and disposable. Things are built with web tech so engineers can be found to work on apps easily. That's OK because new software isn't generally impacted by Y2038, but in businesses where there are old, legacy systems run by people who have a modern attitude to software ownership, things will fail because those businesses won't see importance of the threat.

[aaron_m04]

> [...] but in businesses where there are old, legacy systems run by people who have a modern attitude to software ownership, things will fail because those businesses won't see importance of the threat.

How common will that be, though? I would expect that "cheap and disposable" software would mean most software in the year 2038 would be recently written, which would mean the programmers would be aware of the impending 32-bit rollover issue.

[cookingrobot]

On the one hand, most programmers are writing at a higher level, and probably have no ability to fix or even work around a date rollover issue.

On the other hand, a few fixes at lower levels will correct it for everyone above them.

[dastbe]

individual software is more disposable, but the systems themselves still have immense value. the software in the system will be updated or replaced (because it is easier to do so!) if it’s valuable for the system.