Just like y2k, the irony is the problem is already solved but that won’t help us.
Datetime types have long since converted to longer data types that will not have such a problem for thousands of years. APIs have long since converted to return those longer data types. The problem is solved.
But the backward compatible 32bit datetime types are still there. Too many programs still use them. Too many embedded devices don’t include “extra features that waste space “, industrial devices are far more widespread but don’t get updates for many years. Worst of all, we have no idea what works and what doesn’t. We’re doomed to repeat the same crisis as y2k, where we’ll need to evaluate all our software, roll out patches, worry about everything falling down.
Modern software development has made it easier than ever to keep everything up to date, to prevent so many issues from ever happening. Year 2038 is an unnecessary problem. But human nature is to let it fester until the problem erupts. We’re doomed
Just like y2k, the irony is the problem is already solved but that won’t help us.
Datetime types have long since converted to longer data types that will not have such a problem for thousands of years. APIs have long since converted to return those longer data types. The problem is solved.
But the backward compatible 32bit datetime types are still there. Too many programs still use them. Too many embedded devices don’t include “extra features that waste space “, industrial devices are far more widespread but don’t get updates for many years. Worst of all, we have no idea what works and what doesn’t. We’re doomed to repeat the same crisis as y2k, where we’ll need to evaluate all our software, roll out patches, worry about everything falling down.
Modern software development has made it easier than ever to keep everything up to date, to prevent so many issues from ever happening. Year 2038 is an unnecessary problem. But human nature is to let it fester until the problem erupts. We’re doomed