Y2K Bug
Images are sometimes not shown due to bandwidth/network limitations. Refreshing the page usually helps.
You are currently reading a thread in /g/ - Technology
You are currently reading a thread in /g/ - Technology
16 years ago tonight the media had spread fears over the Y2K Bug. Were you worried?
>>52165768
Nah. I was sitting at my neighbors house drinking pineapple juice. I was only 9 at the time, and didn't really see what the big deal with some numbers flipping over was.
>>52165768
i wasn't alive :^)
>>52165768
Lots of people got very rich doing Y2K certification runs. Selling Y2K compliance scanners etc.
All disappeared in early Jan 2000.
>>52165768
>16 years ago tonight the media had spread fears over the Y2K Bug
No, the media started the bullshit in the beginning of the 90s
Also my fathers job back then was to fix this bug in many COBOL programs, whole companies would have been ruined if it would not have been fixed
>>52165768
I stocked up with ten liters of water and some food for my guinea pig.
I was 15
>>52165832
...Haha funny bait
>>52165768
I was a teenager and was hoping for some kind of apocalypse beginning with a Fight Club like erasing of debt and similar events. Of course I didn't actually have any debt as a teenager, but that's just how I thought.
>>52165768
Not really. The worst that would have happened to any system I had anything to do with is the system clock being wrong. And the claims that it would cause global infrastructure to fail and nuclear weapons to launch themselves and all that always smelled like bullshit to me, so I wasn't really worried about that either.
>>52165886
So it's your dad's fault we all survived! F your dad!
>>52166056
You can kill yourself at any time m8. You can do it!
>>52165973
Ariane 5 flight 501 exploded due to an integer overflow. A div-by-zero caused the USS Yorktown to go still in the water.
It's not hard to write code that fails catastrophically on Y2K, and who knows what they fixed in the billions spent on this
>>52165953
You sounded like a gigantic insufferable faggot. Not much has changed.
We made much money checking bios for business. https://youtu.be/RLUPBetKNmI
>>52166098
Why did they remove a random ISA card? Why did they change a setting in the registry?
What the fuck?
>>52166159
Why? Because why to k, ok?
>>52166096
>Goes around the internet anonymously name-calling insufferable faggot.
>>52165832
>>52165768
I still use shit from before Y2K and none of it has even the slightest issue handling a date after 2000
>his main board has no Y2k compliant marking
I was 7 years old, I'm afraid. Apparently I lived through a few apocalypses in my lifetime. After the world didn't end in 2012, I kind of realized that doomsayers are all spewing bullshit, and there's not much to convince me otherwise anymore.
>>52166248
Even my fucking 286 PC works fine with the current date
>>52165768
Worked at a bank. Had to go in the next morning new years day and test shit.
Everything was fine except for the credit card machine posting 1900.
>>52165832
Raported
>>52165768
I just set my computers clock back to 1901
>>52165768
I was mildly worried.
I had actually been asked to program the Y2K bug in summer 1981 by my intership employer. I said "But won't this stop working in the year 2000?" and the response was "Oh yeah, we all know about that but this software will be long dead by the time that rolls around."
But over the years since then it seemed like no one was really taking it seriously until about 1996 or so. That's when I started hearing about policies and procedures for Y2K certification.
Actually I don't think I heard the acronym Y2K until about 1998.
In the end there was so much hype about how horrible it was going to be that all of the major companies had already addressed it. So the hype actually worked, it got ppl to fix their shit.
It was Computer Science's finest hour.
>>52165768
Only 22 more years until the 32bit Unix timestamp overflows.
>>52165973
This, I was 13 and considered myself more tech literate than I do now. Seemed like bullshit at the time.
>>52165768
I was 8 and was playing SSB while my parents went out and partied.
At the time, all I knew about computers was some VB my mom had taught me on Windows 98 and screwing around with Mac OS 8 at school.
Pretty sure my school hadn't updated to OS 9 yet. Didn't really care anyway.
Just wait until y3k when technology has advanced to godlike levels.
>>52167014
The "internet of things" will be interesting to witness when all of those "things" start to malfunction
>>52165832
underage detected
MODS
O
D
S
>>52167375
>l y3
y3k? what you do mean?
>>52165768
dafaq is Y2K? I was only a healthy outgoing kid back then.
>>52166232
insufferable faggot detected
>no one mentioned year 2038 problem yet
>be such an autistic fuck to introduce it to the thread with greentext
>>52167535
normie get out reeeeeeeeeeeee
>>52167563
>Can't read but greentexts anyway
>>52167014
>>52165768
I was having a blast at disney world, so no.
>>52167563
>Implying the last of 32 bit processors wouldn't have fried by then
>>52167693
underage b&
gtfo you lil cunt
>>52165832
Fucking zombies man.
>>52167563
>2016
>not greentexting
>>52166080
A lot of code today fails thanks to DST change
>Not worrying about Y2K38
>>52166080
Meanwhile redhat reported that i recieved a cookie that would expire in 1967.
>in 2 years people born in 2000 will be allowed to post on 4chan
>>52171284
>Implying they don't do it anyway
I started coming here when I was 13, I'm sure some other people are as autistic as me
>>52167014
It has already 64bits where it can.
>>52165768
>brother works in support for big software company
>actually bought a "Y2K survival kit" and feared for his computer
>mfw
>>52171349
I don't really understand how this is really a thing. Just set your PC clock to the last day of 2000 to see if you get an error.
>>52172130
It's not like you could do that for the computers used by your bank.
>>52166255
Thas dope anon. Didn't ever see this before.
Y10k bug
Y100k bug
Y....
>humanity ever learning a lesson
>>52165784
this
>>52170912
That time travel.
>>52165768
nah, John Titor fixed that shit for us
based Titor
>>52166255
Dat AGP 2x 3.3V tho
>>52169548
Cite your sources, sounds like horseshit to me.
![Year_2038_problem[1].gif](https://i.imgur.com/mpgH2Ys.gif "Year_2038_problem[1].gif")
I was 6 and playing with some figures I had while my dad spent the entire year worrying about his job and what was going to happen. It just sounded stupid to me at the time because I was a little kid.
>>52171295
I've been here since I was 14-15, around 2007-2008. Only lurked for a year or two because I didn't want to post like a retard and because that was around the time when my family could afford a PC just for me so I was still learning the ropes.
>>52174013
So we'll invent time travel in 2038?
>>52174107
most definitely
>>52165832
girl ?
>>52166255
I've still got a few AGP boards laying around, nicely done.
>>52165768
>Were you worried?
No.
>>52165784
>pineapple juice
Oh my God anon.
>>52165768
i wasn't too worried, i didn't expect everything to explode, but i did expect more than what happened
>>52165832
>>52174516
This rule killed easy cp.
Fucking cucks
>>52174549
1. It never stopped any underage people posting their body parts
2. There's another rule that bans underage body parts. Notably the ones that specify that no illegal material is allowed.
I don't understand a number as simple as 2000 could cause a bug.
>>52174594
It wasn't stored as a 4 digit number.
It was stored as a 2 digit number.
1999 was stored as 99.
1900 was stored as 00
Programs that relied on knowing the right date would freak out.
>>52174594
1999 = year 99
2000 = year 00
00 = 1900
>>52174594
many systems assumed the year began with "19", since that's all the systems had seen
so you'd end up with dates rolling over to "19100" (assumed "19", then 99+1), or "1900" (99 wrapping around to 00)
then other things that work with dates freak out because of the unexpected year (first jumps forward ~17k years, plus is 5 digits, even more systems assume a 4 digit year max. second goes back in time)
>>52174594
Basically, there are a lot of functions and etc that depend on dates, exorbitant when it comes to databases and such. As a shortcut, instead of using the full 4 digits for the great a lot of people used just the last two digits. It wasn't really that crazy or stupid, it was just a linguistic norm. It had been 19xx for almost a hundred years, so people would use "98" instead of "1998" or they would say "back in 84..." instead of "back in 1984..."
But the thing is, people didn't really consider that rolling over to "00" is not useful for a computer. If course people know that it's 2000 because we have all kinds of context that tells us that it is the year 2000. A computer doesn't work that way.
>>52174576
Yeah, I know, I just tried to shitpost, but failed.
Sorry.
I was too tech illiterate back then to understand it all, but thankfully the media here in Finland isn't as sensationalist as it is in murrica so they also lead people who weren't all "THE WORLD IS GOING TO END!!!" talk and calm people down.
I've spoken to several people who were working on ensuring the "y2k compliance" of systems and they always claim that we averted disaster because of them. However when you ask them if they actually found any errors to sort out they end up ether avoiding the question or admitting that they didn't find anything.
Worst stuff I've heard have been about supermarkets accidentally throwing out food because of their age being calculated incorrectly or or people being born in the first few years of the 1900's getting automatic invitations to school or kindergarten. If there had been any serious problems, obviously one or more of them would not have been corrected.
>>52167522
year 3000
>>52167375
unfortunately since computers have seen a change in millenium, this won't happen again in 3000
there is the 2038 one though (32bit unix time)
though the only thing that will affect is someones' godly uptime on a dust collector
>>52167522
>not knowing what ythree means
h3h3h3
Everyone was worried!
I was at a New Year's Eve party at a friend's home and a girl working at a hospital had to leave because some machines stopped working
My dad's software for his shop had some errors too, but it was ancient
>>52166248
the one issue I remember is Windows 3.x's file manager showing post 2000 dates wrong, but it still worked fine
>>52165768
I was 10 at the time. I didn't really know much about it other than I kept seeing novelty candles with "Y2K" printed on them at the market. Pretty much the only thing I did technology-wise was play rollercoaster tycoon on the family computer.
I was 2 years old so probably playing with toys or something. Don't think I was worried.
I was 6 and the most advance tech I owned was a gameboy color. Didn't know what Y2K was until years later even though cartoons referenced it all the time.
>>52175037
I was 12, and even I knew that the Y2K bug was stupidly hyped nothing, since the affected systems were long since phased out of the most important things that were computerized at the time.
tl;dr: you're a dumbass
>>52165832
OMG ANON IS GHOST
Aftermath. Did anything even remotely crucial went down due to Y2K-bug? Or at least bugged?
>>52165886
>Also my fathers job back then was to fix this bug in many COBOL programs, whole companies would have been ruined if it would not have been fixed
Ditto
Nah, I was like 8 years old and had that Game Boy Color.
I knew it'd never let me down.
>>52165832
Reported
>>52175334
No need to be so salty anon.
>>52175436
I think some bank in Germany had big losses, but I'm not going to bother looking for evidence.
>>52174013
That's just another overhyped thing
i tried this on 32-bit many years ago when i first heard about it.
No such thing happened.
>>52174594
>>52174636
>>52174646
This is actualy 2k38 bug.
Tried this with many programs and even some phones. Turned out when you type in number 00-38 it uses prefix 20, when you type in 39-99 it uses 19 as a prefix.
