I know this isn’t any kind of surprise, and yet, well…
- 018118055 ( @018118055@sopuli.xyz ) 30•7 months ago
2100 and 2400 will be a shitshow
- Papamousse ( @Frederic@beehaw.org ) 16•7 months ago
2038 will certainly be a shit show
- flameguy21 ( @flameguy21@lemm.ee ) English7•7 months ago
Yeah but I’ll be dead so not my problem lmao
- deegeese ( @deegeese@sopuli.xyz ) 6•7 months ago
Nah.
Same thing happened in 2000 and it was a mouse’s fart.
- 018118055 ( @018118055@sopuli.xyz ) 13•7 months ago
Because of months of preparation. I know, I was doing it.
- deegeese ( @deegeese@sopuli.xyz ) 3•7 months ago
And now that every time library has been updated, we’re safe until our grandchildren reimplement those bugs in a language that has not yet been invented.
- 018118055 ( @018118055@sopuli.xyz ) 8•7 months ago
I’ve already seen reimplementation of 2 digit dates here and there.
- deegeese ( @deegeese@sopuli.xyz ) 4•7 months ago
LOL fuck those guys.
- 018118055 ( @018118055@sopuli.xyz ) 3•7 months ago
Fortunately I will not be involved. Hopefully I can make something from 2038 though.
- deegeese ( @deegeese@sopuli.xyz ) 1•7 months ago
You’re not the only one forseeing a nice consultant payday there.
- JustCopyingOthers ( @JustCopyingOthers@lemmy.ml ) 3•7 months ago
I went to uni in the mid 90s when Y2K prep was all the rage, went back to do another degree 20 years later. It was interesting to see the graffiti in the CS toilets. Two digits up to about 1996, four digits for a decade, then back to two.
- Midnight1938 ( @Midnight1938@reddthat.com ) 3•7 months ago
Why
- 018118055 ( @018118055@sopuli.xyz ) 15•7 months ago
2100 not a leap year (divisible by 100). 2400 is a leap year (divisible by 400). Developing for dates is a minefield.
- Midnight1938 ( @Midnight1938@reddthat.com ) 1•7 months ago
Now imagine working on non Georgian, and the year is 2060
- 0x4E4F ( @0x4E4F@infosec.pub ) English2•7 months ago
Luckily, none of us will be there.
- Dieguito 🦝 ( @DieguiTux8623@feddit.it ) 10•7 months ago
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?
- Papamousse ( @Frederic@beehaw.org ) 7•7 months ago
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.
- TostiHawaii ( @TostiHawaii@feddit.nl ) 4•7 months ago
I hope leap days are handled a bit more sophisticated!
- Scrollone ( @Scrollone@feddit.it ) 6•7 months ago
Insert black frames for 24 hours and you’re good to go!
- Papamousse ( @Frederic@beehaw.org ) 2•7 months ago
Haha yes, no problem with those 😁
- 👍Maximum Derek👍 ( @Bishma@discuss.tchncs.de ) English7•7 months ago
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.
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.
- 👍Maximum Derek👍 ( @Bishma@discuss.tchncs.de ) English4•7 months ago
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.
- macniel ( @DmMacniel@feddit.de ) 3•7 months ago
Yeah… I patched some unit tests…
- rolaulten ( @rolaulten@startrek.website ) 2•7 months ago
We found an use case with Page duty and it’s ical feed already…