this post was submitted on 10 May 2025
1103 points (97.6% liked)
memes
14674 readers
5293 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads
No advertisements or spam. This is an instance rule and the only way to live.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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