Xaerxiessia
Lost in Translation
If you don't transfer right away , you gonna loose everything at reboot !!!
What a joke.
What a joke.
I loved the Y2K bug (and the anxiety it caused local, state and federal agencies).Who remembers the hysteria about the Y2K bug ?
// The cost to fix the Y2K bug is estimated to have been between $300 billion and $600 billion globally, with the United States alone spending around $100 billion. //
ChatGPT is your friend![]()
It was never a hysteria.If you don't transfer right away , you gonna loose everything at reboot !!!
What a joke.
I sometimes feel like people are allergic to planning ahead. Recognizing there is a flaw and spreading the information and making plans to prevent the flaw from becoming a Problem is a good thing, not hysteria.It was never a hysteria.
A lot of money and resources was spent to make sure nothing bad happened before the century turned. That is why nothing happened.
There were a lot of bad things that happened during and after Y2K, the general public doesn't remember or didn't care because the world didn't end and it didn't necessarily impact them, per se.It was never a hysteria.
A lot of money and resources was spent to make sure nothing bad happened before the century turned. That is why nothing happened.
I remember waking up 1/1/2000 and thinking, 'ah, that's a shame'. But I teeter between chaotic neutral and chaotic evil.
CHAT GPT is NEVER your friend!! This will be your failing!!Who remembers the hysteria about the Y2K bug ?
// The cost to fix the Y2K bug is estimated to have been between $300 billion and $600 billion globally, with the United States alone spending around $100 billion. //
ChatGPT is your friend![]()
Yeah, I had to continue to deal with my idiot neighbors survival. It was a massive rip off, I had a plan!There weren't even any zombies. Worst apocalypse ever.
- One of the more "fun" things we helped fix was Lotus123 for the federal govt.
~Loki
DOOOOOOOMAs the weirdo who privately owned a computer, I was tasked with that y2k stuff in our department, nothing world-breaking but some documentation would go awry if there actually were any production in the night of dec 31 (like the heat-treatment after certain production processes missing the 3h deadline, or the sudden realisation that that unique part number used in 1999 was already used back in 1970.)
But yeah, there was a lot of angst back then, and it was frustrating, as an 18 years old trying to convince folks in their 50's that very little will happen.
Well, now I'm in my 50's and Y2K38 will be our doom, I tell you!
As the weirdo who privately owned a computer, I was tasked with that y2k stuff in our department, nothing world-breaking but some documentation would go awry if there actually were any production in the night of dec 31 (like the heat-treatment after certain production processes missing the 3h deadline, or the sudden realisation that that unique part number used in 1999 was already used back in 1970.)
But yeah, there was a lot of angst back then, and it was frustrating, as an 18 years old trying to convince folks in their 50's that very little will happen.
Well, now I'm in my 50's and Y2K38 will be our doom, I tell you!
I miss sharing processor time on my old mainframes. :cry:Ahhhhhhhhhhh!!1!!1!1111!!!!!!! The UNIX EPOCH DISASTER!!!!1!11!!1!!! AHHHHHHHHHHHHHHHHH!1!!!1!!1!111!!!!1!!1!!!!1!!!!!!!!!!!!!!
Edit: Added 1s to the exclamations to clarify how scary this will be