...s, whereupon we face a calamity the likes of which haven't been seen since Y2K. -- [[User:IronyChef|IronyChef]] ([[User talk:IronyChef|talk]]) 06:33, 20 N
I haven't been this disappointed by the apocalypse since Y2K. Not even worth a rental. [[Special:Contributions/69.127.136.211|69.127.1
3 KB (497 words) - 15:38, 15 October 2022
| 32-bit timestamps roll over, causing Y2K-level chaos
::32-bit timestamps role over, causing Y2K-level chaos
51 KB (7,042 words) - 20:12, 1 February 2024
...on computers means the bug could affect many more vital systems, but with Y2K passing by relatively uneventfully especially in light of the hype that pre
:Cueball: Remember Y2K? This could be even ''worse!''
3 KB (417 words) - 21:47, 13 December 2023
...6%2flow patents]. There was even a pair of these that were installed circa Y2K in the Paris subway (Châtelet-Les-Halles, IIRC), which is renowned for its
9 KB (1,369 words) - 14:26, 19 May 2018
...but have only used 2-digit years - e.g. 27 Feb 13 (they didn't learn from Y2K!) {{unsigned|64.140.113.219}}
...pean' (well, for ''part'' of my life, being in the UK) and being active in Y2K mitigation across a US-owned corporation. I normally default to DD/Mmm/YYY
18 KB (2,768 words) - 02:03, 10 February 2024
..." part was a pun because things will roll over 136 years instead of 100 as Y2K did. I don't want to add it without discussion first [[Special:Contribution
I never really understood why people were worried about the Y2K bug. At worst, surely it would just interpret it as 1900 instead of 2000? [
3 KB (363 words) - 15:59, 24 November 2022
...poch boom to hurriedly uplift 32 bit code before the 'end'. Similar to the Y2K boom. I might consider lending my expertise at a considerable markup. :) [[
2 KB (358 words) - 22:36, 16 April 2019
...long-term benefits, rather than only the coming years or decades. The {{w|Y2K problem}} was due to using only two digits to store the year, which would h
4 KB (676 words) - 10:26, 10 November 2023
...k we actually start address that sooner that in September 9999. It will be Y2K over again! .... not sure where will people of 9999 get {{w|Fortran}} and {
...ch 'precision direction', mid-way? Still, as someone who went through the Y2K process ''and'' worked with colleagues across the Atlantic, I tend to use d
12 KB (1,764 words) - 20:40, 26 May 2022
...ical year numbering|astronomical calendars}}, or the {{w|Year 2000 problem|Y2K}} and {{w|Year 2038 problem|year 2038}} problem. Nevertheless in this comic
7 KB (1,089 words) - 21:02, 4 May 2022
{{comicsrow|2697|2022-11-11|Y2K and 2038|y2k and 2038 2x.png}}
29 KB (3,834 words) - 00:45, 9 May 2024
...software update, reconfiguration boo-boo, external attack, frozen process, Y2K+19 bug? [[User:Ianrbibtitlht|Ianrbibtitlht]] ([[User talk:Ianrbibtitlht|tal
9 KB (1,365 words) - 11:05, 9 February 2023
...ry and the 3rd Millenium did not start on 2000-01-01 (even whilst residual Y2K issues with current dates would have) but 2001-01-01.
::But I was happy enough to celebrate Y2K happening (and yet the bugs not, due in a relatively minute but otherwise r
19 KB (3,060 words) - 15:29, 11 February 2024
I'm surprised Y2K hasn't been mentioned. A good example of when we did actually stop a big pr
...s leapt on the name and blew it WAY out of proportion. If nobody had fixed Y2K, what does it matter if this computer or that computer running this program
9 KB (1,360 words) - 17:40, 14 May 2022
...matter in that particular case!) and doing my bit to support the upcoming Y2K-compatability issues that other people were gradually getting to know about
10 KB (1,489 words) - 03:01, 28 July 2023
...hat this limit would be reached. Computers using such systems would have a Y2K-analogous bug once someone actually reached 128 years old, where anomalous
18 KB (2,976 words) - 14:28, 16 April 2024
...ypos, and falsehoods? I noticed something similar happened with the recent Y2K comic. I really don't like to log in because we usually show we can do good
19 KB (2,756 words) - 08:12, 20 December 2023
...in the mistaken belief that the world would come to an end (sort of like a Y2K scare, but without the tech). [[User:Beechmere|Beechmere]] ([[User talk:Be
10 KB (1,419 words) - 10:31, 29 November 2023
#REDIRECT [[2697: Y2K and 2038]]
32 bytes (4 words) - 18:11, 11 November 2022
#REDIRECT [[2697: Y2K and 2038]]
32 bytes (4 words) - 18:11, 11 November 2022
