this post was submitted on 17 Mar 2024
2846 points (99.2% liked)

Science Memes

11161 readers
1513 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 257 points 8 months ago (16 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 77 points 8 months ago (10 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 43 points 8 months ago* (last edited 8 months ago)

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

load more comments (9 replies)
[–] FractalsInfinite@sh.itjust.works 48 points 8 months 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 33 points 8 months ago* (last edited 8 months ago) (5 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 40 points 8 months ago (1 children)

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

[–] Towerofpain11@lemmy.world 11 points 8 months ago

This is the funniest comment I have ever read here. Thank you.

[–] Matombo@feddit.de 9 points 8 months ago

debian for example is atm at work recompiling everything vom 32bit to 64bit timestamps (thanks to open source this is no problem) donno what happens to propriarary legacy software

[–] AdrianTheFrog@lemmy.world 2 points 8 months 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 2 points 8 months 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 8 months 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.

load more comments (1 replies)
[–] Scrollone@feddit.it 15 points 8 months ago (4 children)

2038 is approaching super fast and nobody seems to care yet

[–] Aceticon@lemmy.world 46 points 8 months ago (3 children)

At the rate of one year per year, even.

[–] CybranM@feddit.nu 19 points 8 months ago (1 children)

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

[–] jjjalljs@ttrpg.network 4 points 8 months ago

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

load more comments (1 replies)
[–] Successful_Try543@feddit.de 14 points 8 months ago* (last edited 8 months ago) (1 children)

AfaIk that's not entirely true, e.g. Debian is changing the system time from 32 bit integer to 64 bit. Thus I assume other distros do this as well. However, this does not help for industrial or IOT devices running deprecated Unix / Linux derivatives.

[–] smeg@feddit.uk 18 points 8 months ago (1 children)

industrial or IOT devices running deprecated Unix / Linux derivatives

This is my concern, all the embedded devices happily running in underground systems like pipes and cables. I assume there are at least a few which nobody even considered patching because they've "just worked" for decades!

[–] Scrollone@feddit.it 10 points 8 months ago (1 children)

Or like... PLANES! Some planes still update their firmware using floppy disks

[–] smeg@feddit.uk 10 points 8 months ago

They do at least get updates though, and they're big enough that they don't get forgotten!

[–] exocrinous@startrek.website 9 points 8 months ago

That's not true, lots of people are panicking about how fast they're getting older

[–] theneverfox@pawb.social 3 points 8 months ago

Well that's justifiable. We're not sure if we're even going to make it to then

[–] fine_sandy_bottom@discuss.tchncs.de 41 points 8 months ago (1 children)

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.

[–] Matombo@feddit.de 41 points 8 months ago (2 children)

It's called the prevention paradox: It's when an issue is so severe that it is prevented with proactive action, so no real consequenses are felt so people think it wasn't severe in the first place.

[–] IvanOverdrive@lemm.ee 41 points 8 months ago

Case in point: Measles. It was a thing when I was a kid. Then it wasn't. Now my kids have to deal with Measles because we can't teach scientific literacy.

[–] cqthca@reddthat.com 2 points 8 months ago

that waste of effort cold war... /s

[–] 4am@lemm.ee 20 points 8 months ago (2 children)

“Lol Elon rocket go boom, science isn’t real” is also happening

Stupid people just think they’re the smartest ones in the room now

[–] phoenixz@lemmy.ca 24 points 8 months ago

Elon musk isn't a scientist, he's a scammer who got lucky. That, and an asshole.

[–] Scrof@sopuli.xyz 5 points 8 months ago (3 children)

Well considering Elon situation I wouldn't blame anyone for making fun of his idiotic ventures. Also starship is actually dumb and saying "you expected for it to blow up" is something no real scientist would've said unless they were making a bomb.

[–] CybranM@feddit.nu 9 points 8 months ago

How is Starship dumb exactly? Making a new thing at any extreme of our current capability is going to be hard and its not unexpected when something goes wrong. What would be dumb is if they put human lives on the line

[–] AdrianTheFrog@lemmy.world 3 points 8 months ago* (last edited 8 months ago)

It had no payload on any of its flights. Rockets that have enough time/money put into development to have a reasonable expectation of working on the first try (and don’t have such an ambitious design) normally launch with a payload on their first flight. Sometimes, even those fail on the first few flights. Having the first few of a new rocket design fail before reliability is achieved is common (ex: Astra) and SpaceX’s other rocket, the Falcon 9, is known as the most reliable rocket, I even suspect it achieves landings more often lately than most others do launches.

Starship's last launch went decently well, reaching orbit (which is as far as most rockets go!) but failing during reentry. It is also supposed to be the rocket with the largest payload capacity to low earth orbit, with 100-150 tons when reused and likely 200-300 when expended.

load more comments (1 replies)
[–] neidu2@feddit.nl 20 points 8 months ago* (last edited 8 months ago) (3 children)

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.

[–] FunkFactory@lemmy.world 6 points 8 months ago (2 children)

I kinda wish I knew what it was like working on Y2K stuff. It sounds like the most mundane bug to fix, but the problem is that it was everywhere. Which I imagine made it pretty expensive 👀

[–] brianorca@lemmy.world 6 points 8 months ago

That's a pretty good description. And most software back then didn't use nice date utilities, they each had their own inline implementation. So sometimes you had to figure out what they were trying to do in the original code, which was usually written by someone who's not there anymore. But other times it was the most mundane doing the same fix you already did in 200 other programs.

load more comments (1 replies)
[–] AA5B@lemmy.world 3 points 8 months ago* (last edited 8 months ago)

Most of the y2k problem was custom software, and really old embedded stuff. In my case, all our systems were fine at the OS, and I don’t remember any commercial software we had trouble with, but we had a lot of custom software with problems, as did our partners

[–] Dasnap@lemmy.world 3 points 8 months ago

And that modem was handling the nuke codes, right?

load more comments (11 replies)