this post was submitted on 17 Mar 2024
145 points (97.4% liked)

Science Memes

16603 readers
880 users here now

Welcome to c/science_memes @ Mander.xyz!

A place for majestic STEMLORD peacocking, as well as memes about the realities of working in a lab.



Rules

  1. Don't throw mud. Behave like an intellectual and remember the human.
  2. Keep it rooted (on topic).
  3. No spam.
  4. Infographics welcome, get schooled.

This is a science community. We use the Dawkins definition of meme.



Research Committee

Other Mander Communities

Science and Research

Biology and Life Sciences

Physical Sciences

Humanities and Social Sciences

Practical and Applied Sciences

Memes

Miscellaneous

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] qjkxbmwvz@startrek.website 5 points 1 year ago (5 children)

Similar with Y2K


it was only a nothingburger because it was taken seriously, and funded well. But the narrative is sometimes, "yeah lol it was a dud."

[–] TonyTonyChopper@mander.xyz 5 points 1 year ago (2 children)

All this hysteria over nuclear weapons is overblown. We've known how to build them for 75 years yet there hasn't been a single one detonated on inhabited American soil. They're harmless

[–] Killing_Spark@feddit.de 2 points 1 year ago* (last edited 1 year ago)

You even dropped a few accidentally and nothing happened! Complete duds these things really

[–] robotica@lemmy.world 1 points 1 year ago (1 children)

Yeah but not all people live on American soil...

[–] TonyTonyChopper@mander.xyz 1 points 1 year ago

It's the American tradition to ignore that

I can't remember the name but I think this is some kind of paradox.

Like the preventative measures we're so effective that they created a perception that there was no risk in the first place.

[–] FractalsInfinite@sh.itjust.works 1 points 1 year ago (2 children)

The question is, what will happen in 2038 when y2k happens again due to an integer overflow? People are already sounding the alarm but who knows if people will fix all of the systems before it hits.

[–] zik@lemmy.world 2 points 1 year ago* (last edited 1 year ago) (3 children)

It's already been addressed in Linux - not sure about other OSes. They doubled the size of time data so now you can keep using it until after the heat death of the universe. If you're around then.

[–] lowleveldata@programming.dev 3 points 1 year ago

Finally it'd be the year of desktop linux with all the windows users die off

[–] AdrianTheFrog@lemmy.world 1 points 1 year ago

I think everything works in windows but the old windows media player. You can test it by setting the time in a windows VM to 2039.

[–] dev_null@lemmy.ml 0 points 1 year ago (1 children)

Obviously new systems are unaffected, the question is how many industrial controllers checking oil pipeline flow levels or whatever were installed before the fix and never updated.

[–] CLOTHESPlN@lemmy.world 2 points 1 year ago

Being somewhat adjacent to that with my work, there is a good chance anything in a critical area (hopefully fields like utilities, petroleum, areas with enough energy to cause harm) have decently hardened or updated equipment where it either isn't an issue, will stop reporting tread data correctly, or roll over to date "0" which depending on the platform with industrial equipment tends to be 1970 in my personal experience. That said, there is always the case that it will not be handled correctly and either run away or stop entirely.

[–] Scrollone@feddit.it 0 points 1 year ago (1 children)

2038 is approaching super fast and nobody seems to care yet

[–] Aceticon@lemmy.world 3 points 1 year ago (1 children)

At the rate of one year per year, even.

[–] CybranM@feddit.nu 3 points 1 year ago (1 children)

For each second that passes we're one second closer to 2038

[–] jjjalljs@ttrpg.network 1 points 1 year ago

Except for leap seconds. Time is the worst to work with :(

[–] neidu2@feddit.nl 1 points 1 year ago* (last edited 1 year ago)

I wasn't working in the IT field back then, as I was only 16, but as I knew that it'd most likely be my field one day (yup, I was right), I followed this closely due to interest, and applied patches accordingly.

Everything kept working fine except this one modem I had.

[–] Tranus@programming.dev -1 points 1 year ago (4 children)

Y2K specifically makes no sense though. Any reasonable way of storing a year would use a binary integer of some length (especially when you want to use as little memory as possible). The same goes for manipulations; they are faster, more memory efficient, and easier to implement in binary. With an 8-bit signed integer counting from 1900, the concerning overflows would occur in 2028, not 2000. A base 10 representation would require at least 8 bits to store a two digit number anyway. There is no advantage to a base 10 representation, and there never has been. For Y2K to have been anything more significant than a text formatting issue, a whole lot of programmers would have had to go out of their way to be really, really bad at their jobs. Also, usage of dates beyond 2000 would have increased gradually for decades leading up to it, so the idea it would be any sort of sudden catastrophe is absurd.

[–] TheOctonaut@mander.xyz 1 points 1 year ago (1 children)

The issue wasn't using the dates. The issue was the computer believing it was now on those dates.

I'm going to assume you aren't old enough to remember, but the "only two digits to represent the year" issue predates computers. Lots of paper forms just gave two digits. And a lot of early computer work was just digitising paper forms.

[–] Scrollone@feddit.it 2 points 1 year ago

I remember paper forms having "19__" in the year field. Good times

[–] bufalo1973@lemmy.ml 1 points 1 year ago

Look some info on BCD or EBCDIC.

[–] frezik@midwest.social 1 points 1 year ago

With an 8-bit signed integer counting from 1900...

Some of the computers in question predate standardizing on 8 bits to the byte. You've got a whole post here of bad assumptions about how things worked.

[–] SkippingRelax@lemmy.world 1 points 1 year ago

a whole lot of programmers would have had to go out of their way to be really, really bad at their jobs.

You don't spend much time around them, do you?