You're viewing a single thread.
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.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.
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.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)
It's not 32 bit computers, but computers with a 32 bit BIOS clock. There is fortunately a difference.