ArchiveSCV
the-signal.com. The Santa Clarita Valley Signal. Back to the collection.

· the-signal.com, Wayback capture

The Y2K glitch was more than just hype

Well, that could have been a lot worse.

And that, really, is the point as the Y2K hype temperature cools. Sure, given the relative success with which the world passed from 1999 into 2000, it’s easy to say the Y2K worries were much ado about nothing.

But that’s not quite correct.

The Y2K worries were about something, alright— but thanks to widespread preventive measures, the potential fallout from the Y2K glitch was substantially minimized. Yes, as in many circumstances, the hype took on a life of its own— reaching absurd proportions in some respects— but the core reason for concern remained legitimate.

Approximately $100 billion was spent in the United States to reprogram and replace computer software and equipment that, over the years, had been set up to recognize dates by the final two digits of the year— 89, 90, and so forth.

In the 1990s, computer experts came to the realization that, when the clock struck midnight on Dec. 31, 1999, those computers could suddenly think the date had clicked over not to 2000, but to 1900. The scenarios if this were to occur ranged from the merely frustrating— your home computer could crash— to the potentially devastating: Power grids could go down, and any technology-dependent business or government service could come to a screeching halt.

As it finally came to pass, the Y2K glitch so far hasn’t been much more than a pretender— a potentially calamitous computer error whose most severe impacts were averted by advance planning.

Obviously, some of that $100 billion was wasteful spending— if not in the business sector, then surely in the government sector. And those who went through “survivalist training” and spent New Year’s Eve camped out in the hills, armed to the gills, went way over the top to be sure.

In a nutshell, those who sensibly dealt with the Y2K glitch— by ensuring their home and business computers were Y2K-compliant — set the stage for the smooth transition we’ve seen.

Still, we’re not necessarily out of the woods yet. Some experts are saying potential Y2K problems exist that won’t become apparent for days, weeks, even months. Compounding the situation is the fact that this is a leap year— so computer watchers are intensely aware of the upcoming arrival of 02-29-00 .

But so far, the indications are good: The sun rose on New Year’s Day, and our ATM’s still worked, our computers didn’t crash and we could still buy gas with a credit card— right at the pump.

Suppose none of that preparation had occurred. At least, we may have seen more instances like the one at a video store in Albany, N.Y., where a customer returned a video and was initially presented with a $91,250 late fee because the video store’s computer thought the return was 100 years late.

The problem, of course, was rectified the old-fashioned way— with pencil and paper— but it’s a humorous anecdote that serves as a reminder of the not-so-humorous problems that could have occurred if we had ignored the hype.

The Signal's opinion is always lableled "Editorial." All other views expressed on the Opinion pages represents individual opinions and are not necessarily those of the newspaper.

← Back to 2000

About this record

How it was held, read and classified

Record details

Morris ID
Not a Morris ID. This record is keyed ts-df:/editorial/signal/0100/010500.html.
System
date-file pages (/desk/MMYY/MMDDYY.html)
Reading copy
the-signal.com
Chosen by: only copy held. On this copy: words 533 (e-mail addresses counted as one token); reader comments 0 (counted, not reproduced here); images 0.
Extracted by
datefile:SLUG_to_rule
signal-extract/0.15 (2026-11-16)

Other copies

Held
None. The holding has this article from one host only.

How it was classified

Label
clearly-local
Judgment
A machine’s (recorded as machine), kept as one so it can be revisited.
Classifier
signal-localclass/0.7 (2026-11-12)
Local signals
  • url:datefile_editorial
National signals
none fired
Scores
local 3, national 0