Quote:
Originally Posted by WarrenC12
This isn't the Y2K problem.  |
Buddy, lets not get into stupid time bugs. I have
the 2038 bug staring me down and I can count the number other calendar bugs we've run into since Y2K with both hands. I unearthed a gem of a Y2K bug last month where the file timestamp was the year 19
101.
Complaining about old software is its own can of worms (like how Apple's pre-System 9 RTC method broke on January 1, 2020) but while Windows has given the ability to let you manually turn DST on and off for decades I got a plate of other things under NDA that either now we have to beg the vendor to update it or start planning bi-annual PM calls to shift the time because it's hard-coded to shift the clock an hour twice a year.
I've always considered removing the time change stupid because it both causes incredible technical problems and was mostly people making excuses about waking up an hour early.
Threaded Mode