people were talking about the millennium bug recently, well it turns out a lot of the fixes just delayed the problem to 2020
"Programmers wanting to avoid the Y2K bug had two broad options: entirely rewrite their code, or adopt a quick fix called “windowing”, which would treat all dates from 00 to 20, as from the 2000s, rather than the 1900s. An estimated 80 per cent of computers fixed in 1999 used the quicker, cheaper option."
"Those systems that used the quick fix have now reached the end of that window, and have rolled back to 1920. Utility company bills have reportedly been produced with the erroneous date 1920, while tens of thousands of parking meters in New York City have declined credit card transactions because of the date glitch."
@radikalgrafitio "Who is still going to use this in 20 years?" - a programmer who is in the middle of fixing an issue created by a programmer that said the exact same thing 20 years before.
@tsturm @radikalgrafitio "The sickly light of a flickering neon sign across the street washed through the slats of the venetian blinds in my office window. Somewhere, the pinched wails of a bluesy sax cried out into the night. I'd sent Dolores home early so I could get some thinking done. By the inch of liquor still left in the bottle, I'd say I'd already thought quite a bit. 'Datetime libraries,' I muttered at the oily swirls of grime on the wall. 'Why is it always datetime libraries?' "
@radikalgrafitio I find it so weird that they were/are encoding dates in decimal. Y2038 makes more sense to me.
@radikalgrafitio I bet they will just kick it back again, so we'll have the same shit happen in 2040
@najimi The good news is 64 bit unix time won't roll over until everyone is on 1024-bit operating systems
@BalooUriza that's the thinking that got us here with the 2038 problem ;P
@najimi And we've basically got it licked already.
@radikalgrafitio -groans and rubs our temples- Of course...
@radikalgrafitio lmao i remember so many tech nerds on reddit getting angry because no one recognised the way they averted y2k. Guess everyone knows now!!
@radikalgrafitio In 1999 I was working for $LARGE_BANK and got occasional glimpses into their Y2K prep. In some cases, software had been running for so long, nobody even knew where the source code was.
@radikalgrafitio With Trumpageddon quickly approaching WWIII, this is thankfully the least of our problems.
@radikalgrafitio that's really nice of them, I was kinda sad I missed the y2k bug! ^-^
Why they did not use at least 50?
I was there!
"Fixing this properly will take a hardware investment of X/code refactoring/some other expenditure"
"We're not going that. Do a hack job, nobody cares about correctness."
But I completely forgot about those meetings until now. Thank you for posting this. I can now tell 20-year-younger me that he was right!
@radikalgrafitio I''m curious what places actually did this. As one who made Y2K fixes, to a soul, none of us ever wanted to have to deal with the mess ever again in our lifetimes. Nobody in any of my circles slapped a 20yr extension on it and shrugged. Sure, there was some windowing to guess the century but every bit of code I saw windowed around the current year, so it would work regardless of the year.
If a company/coder hardcoded 20yrs, let 'em suffer.
"Four digits is too hard."
@radikalgrafitio I guess I just have suffered that suddenly the 1st day of the year the program we have at work stopped printing and previewing. If We change the date of the computer to 2019 it works , but not in 2020. The programmer just fixed it now . It's an old program so I guess that maybe the reason.
@radikalgrafitio Silly developers, always kicking the can down the road. That's what the Linux kernel did.
Lol. I can't believe they couldn't spend a couple more bits of memory to store a date...
Why was that a problem in the first place?
Sunbeam City is a Libertarian Socialist solarpunk instance. It is ran democratically by a cooperative of like-minded individuals.