Jersey Girl wrote:Gunnar wrote:I would not be a bit surprised if even a substantial number of those he successfully appointed as judges eventually turn against him -- more likely sooner than later. I am fairly confident that even a majority of successful conservative judges (even Trump appointed ones) have some sense of ethics and belief in the importance of truth and the rule of law -- despite the deplorable example set by Trump and so many of his associates.
Aside: I remember at this time 19 years ago, the biggest thing on our mind was Y2K. Look where we are now. :-)
I know this is off topic, but many people underestimate the importance of Y2K. Few people realize how many thousands and even millions of man hours were devoted by hard-working computer programmers to find and modify or eliminate problematic computer code that was not compatible with dates beyond the year 2000, or how many potentially serious problems would have been caused by failure to so. So successful was this massive effort that we managed to pass into the new century with hardly a ripple, causing many who were not computer literate to mistakenly conclude that it was never a real problem to begin with. The nations most potentially at risk were those who depended the most on computer technology.
Y2K bugThe Y2K bug was a computer flaw, or bug, that may have caused problems when dealing with dates beyond December 31, 1999. The flaw, faced by computer programmers and users all over the world on January 1, 2000, is also known as the "millennium bug." (The letter K, which stands for kilo (a unit of 1000), is commonly used to represent the number 1,000. So, Y2K stands for Year 2000.) Many skeptics believe it was barely a problem at all.
When complicated computer programs were being written during the 1960s through the 1980s, computer engineers used a two-digit code for the year. The "19" was left out. Instead of a date reading 1970, it read 70. Engineers shortened the date because data storage in computers was costly and took up a lot of space.
As the year 2000 approached, computer programmers realized that computers might not interpret 00 as 2000, but as 1900. Activities that were programmed on a daily or yearly basis would be damaged or flawed. As December 31, 1999, turned into January 1, 2000, computers might interpret December 31, 1999, turning into January 1, 1900.
Banks, which calculate interest rates on a daily basis, faced real problems. Interest rates are the amount of money a lender, such as a bank, charges a customer, such as an individual or business, for a loan. Instead of the rate of interest for one day, the computer would calculate a rate of interest for minus almost 100 years!
Centers of technology, such as power plants, were also threatened by the Y2K bug. Power plants depend on routine computer maintenance for safety checks, such as water pressure or radiation levels. Not having the correct date would throw off these calculations and possibly put nearby residents at risk.
Transportation also depends on the correct time and date. Airlines in particular were put at risk, as computers with records of all scheduled flights would be threatened after all, there were very few airline flights in 1900.
Y2K was both a software and hardware problem. Software refers to the electronic programs used to tell the computer what to do. Hardware is the machinery of the computer itself. Software and hardware companies raced to fix the bug and provided "Y2K compliant" programs to help. The simplest solution was the best: The date was simply expanded to a four-digit number. Governments, especially in the United States and the United Kingdom, worked to address the problem.
In the end, there were very few problems. A nuclear energy facility in Ishikawa, Japan, had some of its radiation equipment fail, but backup facilities ensured there was no threat to the public. The U.S. detected missile launches in Russia and attributed that to the Y2K bug. But the missile launches were planned ahead of time as part of Russias conflict in its republic of Chechnya. There was no computer malfunction.
Countries such as Italy, Russia, and South Korea had done little to prepare for Y2K. They had no more technological problems than those countries, like the U.S., that spent millions of dollars to combat the problem.
Due to the lack of results, many people dismissed the Y2K bug as a hoax or an end-of-the-world cult.
Maybe the consequences of doing nothing would not have been as bad as feared, but you can't very well argue with the sentiment "Better safe than sorry." One of the typical potential problems I read about was exposed by a computer simulation in a sewage plant in Hawaii that proved that not correcting their operating software would have caused an important control valve to open at an inappropriate time, resulting in a massive sewage spill when the calendar changed to the year 2000.
One older computer I had at the time simply refused to work properly, after the beginning of 2000, until I manually reset its internal calendar back to before 2000.
