Oct 22, 2023 · The good thing about Y2K was it had a potential HUGE effect, could be tested for easily, was a limited well-defined problem, and didn't need a COMPLETE fix to work. If a system read 99 as …

Nov 28, 2022 · eli5: How did we solve the Y2K bug? I understand what the general issue was for y2k. Computer systems that only recorded the last two digits of the year would reset to 01 Jan 1900 and …

Jun 19, 2020 · Y2K wasn't a false alarm - it was a serious bug with how years were stored and calculated (specifically using only 2 digits instead of 4) and it was going to cause issues come 1 …

May 25, 2022 · The Y2K work will have removed quite a lot of the worst offenders. I fixed a load of C in the late 1990s (mostly assumptions about tm_year being in the range 0..99) and while I was in there …

Jan 19, 2023 · Fifteen years from now, a bug known as “the year 2038 problem” (also known as Y2038, Y2K38, or the Epochalypse) is expected to cause issues in representing time for certain computer …

Do you think 2038 will become another Y2K situation? I'm not making this a poll because I want something more in depth. The way that UNIX computer systems count time is with a 32-bit method. …

Y2K wasn't really solved, at least the way I want to use the word 'solved.' We knew what the problem was well before it was going to be a problem. The solution was to replace everything using the 2-digit …

A month before Y2K he was put into an artificial coma and cooled down to a near cryogenic easily sustained long term life support. Unfortunately the life support notification system had a Y2K bug, …

Jun 10, 2021 · Y2K problems in embedded systems were pretty rare. Most embedded systems don't even have a real-time clock, and as you said, a 2-digit decimal representation of the year doesn't …

Dec 27, 2023 · The Portal for Public History. Please read the rules before participating, as we remove all comments which break the rules. Answers must be in-depth and comprehensive, or they will be …