651
In the year 2050
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 Dec 2024
651 points (97.7% liked)
memes
10547 readers
2648 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.
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
It's not about having accurate dates, it's about how unix time is used in programming. For some systems that reference unix time for essential calculations, that value rolling over and overflowing would cause catastrophic problems
Sure but that means a workaround for machines affected, but not needing correct dates could be to set their clocks to midnight Jan 1 1970 and have another 65 years to sort it out
Anyway, the biggest problem will be embedded systems, including many household and business smart devices. Several I have are definitely 32 bit machines and might use 32 bit time precise to the second. Some I don't know. I have no idea what processor my TV uses