The Y2K 2038 problem

harangzsolt33 has asked for the wisdom of the Perl Monks concerning the following question:

Replies are listed 'Best First'.
Re: The Y2K 2038 problem by eyepopslikeamosquito (Archbishop) on Mar 18, 2024 at 02:55 UTC
A quick google indicates the Year 2038 problem was fixed in Perl v5.12.0. I suspect the Year 2038 problem will bite only recalcitrant rebels who enthusiastically endorse ancient unsupported software (sorry, couldn't resist :-). 👁️🍾👍🦟	[reply]
Re^2: The Y2K 2038 problem by Bod (Parson) on Mar 18, 2024 at 21:36 UTC
I suspect the Year 2038 problem will bite only recalcitrant rebels... We'll have to wait to find out!	[reply]
Re^3: The Y2K 2038 problem by eyepopslikeamosquito (Archbishop) on Mar 18, 2024 at 22:00 UTC
We'll have to wait to find out! If we're still breathing ... as alluded to at Perl v5.12.0, "It may not mean much to you, but your kids will love it!" :-) 👁️🍾👍🦟	[reply]
Re^2: The Y2K 2038 problem by harangzsolt33 (Deacon) on Mar 19, 2024 at 03:33 UTC
Not funny. Hmmm... Well, I just saw this article, and I'm not sure how it might affect Perl, but I thought I would ask. Back in 1999, I remember, I set my computer's date to Dec. 31, 1999 12:59 to see what happens to it. Nothing happened, which is what I expected. So, although I think, I was using MS-DOS 6.2 at the time, I experienced no issues whatsoever on my computer. This is not to say that DOS was unaffected, but to me it made no difference. So, as long as you use an old software in a way that you avoid its glitches if you know what they are, it's ok. It might work.. but I'm no expert, so... (?)	[reply]
Re^3: The Y2K 2038 problem by eyepopslikeamosquito (Archbishop) on Mar 19, 2024 at 05:00 UTC
Back in 1999, I remember, I set my computer's date to Dec. 31, 1999 12:59 to see what happens to it. Nothing happened, which is what I expected. AFAIK, the Year 2000 problem was nowhere near as catastrophic as many had predicted. There was perhaps a conflict of interest back then because Y2K scaremongering was generating a lot of money for Y2K consultants and software companies in the 1990s. For the year 2038, I'm happy to make two Nostradamus-like predictions: The Year 2038 problem will cause far fewer problems than the Y2K problem did. In 2038, you'll still be using TinyPerl 5.8 on 32-bit Windows XP. harangzsolt33, what are your predictions? 👁️🍾👍🦟	[reply]
Re^4: The Y2K 2038 problem by cavac (Prior) on Mar 20, 2024 at 10:15 UTC
Re^4: The Y2K 2038 problem by NERDVANA (Priest) on Mar 20, 2024 at 22:12 UTC
Re^5: The Y2K 2038 problem by afoken (Chancellor) on Mar 20, 2024 at 23:59 UTC
Some notes below your chosen depth have not been shown here
Re^4: The Y2K 2038 problem by harangzsolt33 (Deacon) on Mar 19, 2024 at 15:55 UTC
Re^5: The Y2K 2038 problem by afoken (Chancellor) on Mar 20, 2024 at 07:16 UTC
OT: Rename The Y2K 2038 to the Year of the Horse problem by bliako (Abbot) on Mar 19, 2024 at 13:50 UTC
My kids will definetely love this.	[reply]