Rare Historical Y2k Snow Globe Year 2000 New Years Vintage Computer Geek Nerd
This item has been shown 0 times.
Rare Historical Y2k Snow Globe Year 2000 New Years Vintage Computer Geek Nerd:
THIS LISTING IS FOR A RARE PART OF HISTORY, A Y2K SNOWGLOBE SHOWING A COMPUTER EXPLODING WHEN THE NEW YEARS HIT AT THE BEGINNING OF THE 21ST CENTURY! WHEN I WAS A KID EVERYONE THOUGHT THIS EVENT WOULD BE THE END OF THE WORLD AND AS WE HAVE NOW LEARNED IT WASN'T BUT STILL FOR ANY PROGRAMMER OR HISTORY BUFF THIS IS A VERY RARE VERY COOL COLLECTIBLE INDEED!
IT IS IN GOOD CONDITION WITH ONLY MINOR SIGNS OF WEAR THAT I CAN SEE.
SEE PICS FOR MORE INFO AND BELOW YOU'LL FIND A BRIEF EXPLANATION OF WHAT Y2K WAS!
The Year 2000 problem (also known as the Y2K problem, the Millennium bug, the Y2K bug, or simply Y2K) was a problem for both digital (computer-related) and non-digital documentation and data storage situations which resulted from the practice of abbreviating a four-digit year to two digits.
In 1997, The British Standards Institute (BSI) developed a standard, DISC PD2000-1, which defines "Year 2000 Conformity requirements" as four rules:
- No valid date will cause any interruption in operations.
- Calculation of durations between, or the sequence of, pairs of dates will be correct whether any dates are in different centuries.
- In all interfaces and in all storage, the century must be unambiguous, either specified, or calculable by algorithm
- Year 2000 must be recognized as a leap year
It identifies two problems that may exist in many computer programs.
Firstly, the practice of representing the year with two digits becomes problematic with logical error(s) arising upon "rollover" from x99 to x00. This has caused some date-related processing to operate incorrectly for dates and times on and after 1 January 2000, and on other critical dates which were billed "event horizons". Without corrective action, long-working systems would break down when the "... 97, 98, 99, 00 ..." ascending numbering assumption suddenly became invalid.
Secondly, some programmers had misunderstood the rule that determines whether years that are exactly divisible by 100 are leap years, and assumed the year 2000 would not be a leap year. Although most years divisible by 100 are not leap years, if they are divisible by 400 then they are. Thus the year 2000 was a leap year.
Companies and organizations worldwide checked, fixed, and upgraded their computer systems.
The number of computer failures that occurred when the clocks rolled over into 2000 in spite of remedial work is not known; amongst other reasons is the reticence of organisations to report problems.