this post was submitted on 28 Apr 2024
55 points (96.6% liked)

Ask Lemmy

26734 readers
1461 users here now

A Fediverse community for open-ended, thought provoking questions

Please don't post about US Politics.


Rules: (interactive)


1) Be nice and; have funDoxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them


2) All posts must end with a '?'This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?


3) No spamPlease do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.


4) NSFW is okay, within reasonJust remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected]. NSFW comments should be restricted to posts tagged [NSFW].


5) This is not a support community.
It is not a place for 'how do I?', type questions. If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.


Reminder: The terms of service apply here too.

Partnered Communities:

Tech Support

No Stupid Questions

You Should Know

Reddit

Jokes

Ask Ouija


Logo design credit goes to: tubbadu


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 5 points 6 months ago (1 children)

Year 2030 will not start before year 2029 has ended.
I think it's not til year 2048 that we get the actual Y2K bug at which point I'm a bit less sure.

[–] [email protected] 8 points 6 months ago (2 children)

2038, it's known as the 2038 problem, essentially 32bits computers will run out of bits for counting seconds. This has been fixed on any modern system.

[–] [email protected] 1 points 6 months ago

It's not 32 bit computers, but computers with a 32 bit BIOS clock. There is fortunately a difference.

[–] [email protected] 1 points 6 months ago (1 children)

oh i was just making a stupid joke about 2KB.
I didn't realise there was an actual other y2k problem.

How did they get to a 32 bit problem within only 2038 years?
Oh is it like 32 bit counter of seconds or some dumb shit like that.
Stupid shortcut data structures.
That said I'd better check the RTC module in my arduino alarm clock.
It's a clock module though so i assume it was designed by someone who gives time enough respect to store the data properly.

[–] [email protected] 4 points 6 months ago

Completely missed the joke about 2k being 2048, hahahaha

Here's the wiki page https://en.m.wikipedia.org/wiki/Year_2038_problem

Essentially what happens is that computers measure dates as the number of seconds since Jan 1st 1970 (known as Epoch). 32 bits can only count seconds up to Jan 19 2038, after that it will cause an overflow and reset to zero. Most modern systems use 64 bits for dates even if the processor is 32. Same reason why 32 bit computers shouldn't use more than 4GB of RAM (they can't address it properly)