11 mo. ago • 97%

I think my code will be OK...

I know this isn't any kind of surprise, and yet, well...

54 comments

2100 and 2400 will be a shitshow

42
- Not as much as 2038
  
  35
  
  Yeah that's a different shitshow but agreed it is likely to be worse - like y2k the effects are smeared out before and after the date.
  
  10
  
  Why?
  
  2
- 2038 will certainly be a shit show
  
  16
- Yeah but I'll be dead so not my problem lmao
  
  8
- Luckily, none of us will be there.
  
  3
- Nah.
  
  Same thing happened in 2000 and it was a mouse’s fart.
  
  3
  
  Because of months of preparation. I know, I was doing it.
  
  18
- Why
  
  3
  
  2100 not a leap year (divisible by 100). 2400 is a leap year (divisible by 400). Developing for dates is a minefield.
  
  16
  
  Because they're not leap years but are 0 === year % 4
  
  8
- Won’t the computer’s clock reset every time you go to sleep and stop cranking the power generator?
  
  1
  
  Yeah who knows if our computers are sticks by either date
  
  3
Then there's my code, which didn't even survive the time change.

41
- In every project I've ever worked on, there's been somebody who must have been like, "HurDur Storing timestamps in UTC is for losers. Nyeaahh!"
  
  And if I ever find that person, I'm going to get one of those foam pool noodles, and whack him/her over the head with it until I've successfully vented all my frustrations.
  
  15
  
  I just use a float between 0 and 1 with 0 being 1970 and 1 being the predicted heat death of the universe.
  
  16
  
  The only time using UTC breaks down is when any sort of time change gets involved.
  
  If I say I want a reminder at 9am six months from now and you store that as UTC, a day light savings change will mean I get my reminder an hour early or late depending on where in the world I am
  
  4
- Your code made it to the time change!!?
  
  3
  
  Same... The change from 12 to 1
  
  4
People who haven't had a birthday in almost four years are like

.

19
Programming aside, where I live in Southern Europe we have a tradition according to which leap years bring bad luck. After 2020, I don't know what to expect... nuclear apocalypse maybe?

12
- Wait, 2020 wasn't a bad luck year?
  
  -1
  
  Previous commenter meant "what could be worse than the bad luck leap year 2020?"
  
  7
Always, always, always, without taking any shortcuts, use a tzinfo library for your language.

9
- Anyone who doesn't use standardized libraries for tz should be summarily tried.
  
  3
I'm not worried about my code, I'm (very slightly) worried about all the date libraries I used because I didn't want code that shit again for the billionth time.

7
- Your comment made me go look at the source for moment.js. It has "leap" 13 times and the code looks correct. I assume they test stuff like this.
  
  7
  
  Yeah, I'm generally using the common data/time libraries in most (if not all) languages and I'm pretty sure they've all been through more than 1 leap year at this point. I just never 100% trust the code I don't control - 99.9% maybe, but never 100.
  
  4
I worked in broadcasting (programming broadcasting applications), everything is done with PTP (Precise Time Protocol) and TC (timecode) in video. We had to support leap second, it's not as easy, but in the end, insert black frames for 1s and that's it.

7
- I hope leap days are handled a bit more sophisticated!
  
  4
  
  Insert black frames for 24 hours and you're good to go!
  
  6
  
  Haha yes, no problem with those 😁
  
  2
Yeah... I patched some unit tests...

4
- Before it was 50/50 that they'd fail on leap day, but after the patch it's 50/50.
  
  3
Permanently Deleted

4
I'm not worried at all - I love me some tz database.

2
I hope the homeassistant guys already have this covered, because I didn't use it 4 years ago to know

2
We found an use case with Page duty and it's ical feed already...

1

You've viewed 54 comments.