nixCraft 🐧Dec 30, 2024
You can never be too careful #y2k that was one hell of the new year 😏😂😓 .. yup that was almost 25 years ago 😉
Show threadsatmd
@nixCraft I one had a customer that asked us to turn off als servers for the extra second 23:59:60 some new year's eve. I told them this didn't apply to us as a problem (because sane software just uses monotone-increasing steady time). I offered to be on-call. Well, no call, no problems whatsoever. But I learned that quite some enterprise software has very poor concepts of date and time.


#y2k
Dec 30, 2024 at 10:27pmWeb
Show threadsatmdDec 30, 2024
@nixCraft
I also think I remember parts of an interview with people responsible for the two-digits-for-year in BIOSes. They regretted the decision, but memory was expensive. Today the more clever people favor using the UTC epoch to express time. It's independent of time zones and daylight savings. Quite recently, it was discovered that 32bit linux would have had an overflow in time_t. But luckily, we can expect all devices to support 64bit time_t (or fall apart) in time.