“Whatever happened with the ozone layer panic, if scientists are so smart?”
We listened to the scientists, and the problem went away.
As a kiwi, the amount of sunburn I get every summer would imply it hasn’t.
No, also the massive SO2 that Mt Pinatubo put into the atmosphere slowly went away. And the CFCs.
Pinatubo created more sulfur emissions during its eruption than 10 years of all human coal burning.
And also on top of that we were also wrecking the Ozone.
Nature can always make our mistakes much much worse.
Get that marble brain Reddit-style bs outta here. If you wanna deny, you’re gonna have to come up with a reason that you could be right. Otherwise, we’re just gonna point al laugh at your dumbassery.
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.”
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
WTF?
Unless that was sarcasm that I missed… 100’s of weapons have been tested on US soil…
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.
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.
Finally it’d be the year of desktop linux with all the windows users die off
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.
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.
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.
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.
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.
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 👀
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.
“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
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.
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.
Starship, as it is right now, is already a better rocket than SLS. It can already carry more mass and be cheaper (even fully expended) than the SLS’s 4 billion cost per launch.
It will get better. Falcon 9 didn’t land the first time either, but now it has successfully landed more consecutive times than any other rocket has flown.
There’s nothing wrong with saying this is a test. This is only a test, and we don’t expect it to be perfect yet. Each time they learn from the data. And SpaceX hasn’t repeated the same mistake twice.
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.
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.
You’re thinking of the problem with modern solutions in mind. Y2K originates from punch cards where everything was stored in characters. To save space only the last 2 digits of the year because back then you didn’t need to store the 19 of year 19xx. The technique of storing data stayed the same for a long time despite technology advancing beyond punch cards. The assumption that it’s always 19xx caused the Y2K bug because once it overflows to 00 the system doesn’t know if it’s 1900 or 2000.
When you do things right, people won’t be sure you’ve done anything at all.
Y2K is similar. Most people will remember not much happening at all. Lots of people worked hard to solve the problem and prevent disaster.
Was there ever really a threat to begin with? The whole thing sounds like Jewish space lasers to me.
Edit: Gotta love getting downvoted for asking a question.
Yes, most administrative programs, think hospitals, municipal, etc had a year set only in 2 digits. Yesterdays timestamp will read as 99 years in the future, since the year is 00. Imagine every todo item of the last 20 odd years suddenly being pushed onto your todo list. Timers set to take place every x time can’t check when last something happend. Time critical nuclear safety mechanisms, computers getting stuck due to data overload, everything needed to be looked at to determine risk.
So you take all the dates, add size to store additional data, add 1900 to the years and you are set. In principle a very straight forward fix, but it takes time to properly implement. Because everyone was made aware of the potential issue IT professionals could more easily lobby for the time and funds to make the necessary changes before things went awry.
You’re probably getting down voted because you asked here instead of a search engine, and many people think it’s common knowledge, and it was already answered in this thread.
Sometimes an innocent question looks like someone JAQing off.
It was a massive threat as it would break banking records and aircraft flight paths. Those industries spent millions to fix the problem. In 14 years(2038) we’ll have a similar problem with all 32bit computers breaking if they haven’t had firmware updates to store UTC time as a 64bit number composed of two 32bit numbers. Lots of medical, industrial, and government equipment will need to either be patched or replaced.
I literally had this exact exchange with someone last year, when they tried to cast doubt on global warming by comparing it to the ozone. Another person did the same , using acid rain, and I pointed out that the northeast sued the shit out of the Midwest until they cut that shit with the coal fire power plants.
The Conservative Party led Canadian Government and the Regan-era Republican US Government started working on the US-Canada Air Quality Agreement, which was signed by the George H.W. Bush administration into law in the US (and the Brian Mulroney led Government of Canada).
That’s right — two Conservative governments identified a problem, listened to their scientists, and enacted a solution to acid rain. And now the problem has virtually disappeared.
Oh how low Conservatives have fallen on both sides of the border since those days.
I use talking points like these a fair amount with Republicans. Try to get them to think back to when they were leaders in environmental policy. Get back to their roots of environmental stewardship. It seems to have moved the needle slightly.
Many, unfortunately, are so deep in doublethink the won’t believe that tricky Dick initiated the whole thing with the EPA, clean water or air act, and the endangered species acts. Some came after, i think, but he set it rolling. He was still a bad dude, but he did some good stuff
There were goddamn Nickelodeon phone-a-thons where you pledged to not use cfc products. This shit was serious.
Edit: I just remembered ,they talked about how bad the sun was for kids in Australia, or something.
Australia and New Zealand do not fuck about with sun safety. Even with the improvements in the ozone layer, our skin cancer rates are still way higher than the rest of the world
New Zealand do not fuck about with sun safety.
Except we were kicking the can with sun screen regulation until 2022.
https://comcom.govt.nz/business/your-obligations-as-a-business/product-safety-standards/sunscreen
https://www.legislation.govt.nz/act/public/2022/0004/latest/whole.html
Until this law, sun screen lotion didn’t have to prove that they actually provided the SPF that they claimed.
Yeah I lived in Auckland for a bit, they don’t care as much about sunscreen. More sun safety conscious than Pacific Northwesterners in my experience, but probably closer to that group than myself as a fair-skinned Aussie that’s used to getting burnt after just sitting outside in the shade for awhile
I’d argue that while we are much more diligent than other countries, and regulations are much stronger. The average person doesn’t pay nearly enough attention, and the fact the UV index isn’t required to be mentioned on weather reports, or as prominently or more prominently than the temperature, is a big oversight in my opinion.
I check the UV every time I go outside (other than when it’s died down over winter), just as you’d check the temperature, and I think it’s wild barely anyone else does.
