Background Y2K is a numeronym and was the common abbreviation for the year 2000 software problem. The abbreviation combines the letter Y for "year", the number 2 and a capitalized version of k for the SI unit prefix kilo meaning 1000; hence, 2K signifies 2000. Enough of the system was confused by dates at the Y2K rollover, and it considered 2000 to be anything from 1900, 1901, year 0000 and so on, that ALL data in the system was considered to be aged out because it was more than 7 years from 1999.
That includes backups. Discover the true story of Y2K, the millennium bug. Learn what happened, the preparations taken, and why the feared global computer breakdown never occurred.
Y2K bug, a problem in the coding of computerized systems that was projected to create havoc in computers and computer networks around the world at the beginning of the year 2000. After over a year of international alarm, few major failures occurred in the transition from December 31, 1999, to January 1, 2000. The Y2K bug did actually cause many problems in the United States and around the world.
These problems weren't as widespread as many people expected them to be, but there were enough of them to make us realize that the Y2K bug was a real problem. Zachary Loeb, Purdue University assistant professor, tells NPR's Juana Summers that the real story of Y2k wasn't about computers run amok. It was about experts sounding an alarm, and fixing problems.
Why People Across The World Were Worried About The Y2K Bug The millennium bug, or the Year 2000 bug, is commonly abbreviated as Y2K. It was, at its most basic level, a concern about potential issues with computers as the dates in their systems moved from 1999 to 2000. Discover the fascinating story of Y2K-how a two-digit date nearly caused global panic, what actually happened when the clocks rolled over to the year 2000, and why your microwave didn't start a revolution.
And thanks to this Y2K 2.0, we did get the wonderful irony that was the video game WWE 2k20 ceasing to work in 2k20. Hopefully the fixes this time weren't as lazy, lest we get the Y2038 Bug. Quick overview, this bug is basically because programs won't be able to store a number of years greater than 2038.
Y2K was a success, Grimes said-a demonstration that "we could do big, grand things together as a world." Threats like cyberattacks or quantum encryption breakers won't occur at an agreed upon time, which hinders the kind of large.