Jump to content

Year 2000 problem: Difference between revisions

From Simple English Wikipedia, the free encyclopedia
Content deleted Content added
hecka
Tags: Reverted Visual edit
 
(7 intermediate revisions by 5 users not shown)
Line 1: Line 1:
[[File:Bug de l'an 2000.jpg|thumb|A display in a French engineering school showing the year 1900 instead of 2000. ]]
[[File:Bug de l'an 2000.jpg|thumb|A display in a French engineering school showing the year 1900 instead of 2000. ]]
The '''Year 2000 problem''' (also known as the '''Y2K problem''', the '''millennium bug''', '''Y2K Bug''', and '''Y2K''') was a computer problem that affected lots of computer systems. It happened because of the way in which some early [[computer program]]s were made to handle only years containing two digits (for example '92 instead of 1992). This meant that the computer could confuse the year 2000 with the year 1900, because both would be written as 00. People started fearing that date-related processing would happen incorrectly for dates and times after [[December 31]] [[1999]]. It caused concerns that many [[industry|industries]] (such as [[electricity]] or [[financial]]) and [[government]] functions would stop working at exactly [[midnight]], [[January 1]] [[2000]]. People were panicked by press coverage and media speculation, as well as corporate and government reports. Companies and organisations around the world had to check and upgrade their computer systems to avoid the bug. The preparation for Y2K had a significant effect on the computer industry. No big computer failures occurred when the year changed to 2000. hecker is responsable for this bruhs.
The '''Year 2000 problem''' (also known as the '''Y2K problem''', the '''millennium bug''', '''Y2K Bug''', and '''Y2K''') was a computer problem that affected lots of computer systems. It happened because of the way in which some early [[computer program]]s were made to handle only years containing two digits (for example '92 instead of 1992). This meant that the computer could confuse the year 2000 with the year 1900, because both would be written as 00. People started fearing that date-related processing would happen incorrectly for dates and times after [[December 31]] [[1999]]. It caused concerns that many [[industry|industries]] (such as [[electricity]] or [[financial]]) and [[government]] functions would stop working at exactly [[midnight]], [[January 1]] [[2000]]. People were panicked by press coverage and media speculation, as well as corporate and government reports. Companies and organisations around the world had to check and upgrade their computer systems to avoid the bug. The preparation for Y2K had a significant effect on the computer industry. No big computer failures occurred when the year changed to 2000.


== Similar bugs ==
== Similar bugs ==
Line 8: Line 8:


[[Category:2000]]
[[Category:2000]]
[[Category:Computing]]
[[Category:History of computing]]

Latest revision as of 11:01, 5 July 2023

A display in a French engineering school showing the year 1900 instead of 2000.

The Year 2000 problem (also known as the Y2K problem, the millennium bug, Y2K Bug, and Y2K) was a computer problem that affected lots of computer systems. It happened because of the way in which some early computer programs were made to handle only years containing two digits (for example '92 instead of 1992). This meant that the computer could confuse the year 2000 with the year 1900, because both would be written as 00. People started fearing that date-related processing would happen incorrectly for dates and times after December 31 1999. It caused concerns that many industries (such as electricity or financial) and government functions would stop working at exactly midnight, January 1 2000. People were panicked by press coverage and media speculation, as well as corporate and government reports. Companies and organisations around the world had to check and upgrade their computer systems to avoid the bug. The preparation for Y2K had a significant effect on the computer industry. No big computer failures occurred when the year changed to 2000.

Similar bugs

[change | change source]