Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: rbowman Newsgroups: comp.os.linux.advocacy,comp.os.linux.misc Subject: Re: Can't Avoid That Shit Rust - Even On Gentoo Date: 30 Sep 2024 19:31:08 GMT Lines: 21 Message-ID: References: <5mqdnZuGq4lgwm_7nZ2dnZfqnPSdnZ2d@earthlink.com> <9tDIO.25203$afc4.21891@fx42.iad> <59JIO.96321$WtV9.10707@fx10.iad> <18udnd3mEtEGfGX7nZ2dnZfqnPGdnZ2d@earthlink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: individual.net TopPjBUgbcHD8IFCrtG9hA6b6rL1lmEBuSmfs6SbkFU2BLzuxV Cancel-Lock: sha1:b/Y/GBVc9DPMBjntvqT7fho7ePs= sha256:mnszilFKIpvGZAlrUBQLf3ppBPsJySdIIXlUyJE4FlU= User-Agent: Pan/0.149 (Bellevue; 4c157ba) Xref: csiph.com comp.os.linux.advocacy:671908 comp.os.linux.misc:58756 On Mon, 30 Sep 2024 03:43:16 -0400, 186282@ud0s4.net wrote: > On 9/30/24 3:21 AM, rbowman wrote: >> On Mon, 30 Sep 2024 06:03:29 -0000 (UTC), Lawrence D'Oliveiro wrote: >> >>> Fun fact: I was reworking an old perpetual-calendar program I first >>> wrote back in 1980, to use Fortran 90, a few months ago. And I found a >>> bug in my algorithm that never showed up in any years from the 20th >>> century, but did manifest itself in the 21st century. >> >> Y2K rides again... I think in many cases the problem was recognized in >> the '70s and '80s but nobody expected the code to last decades. > > Very true - and TROUBLESOME. > > We all think in the NOW. With effort we can think a FEW years ahead. > But a whole new century or something similar ... TOO MUCH WORK to > future- proof. We'll "get back to it", sometime ...... It won't be my problem but my bet is there will be a flurry of activity in 2037...