Path: ...!Xl.tags.giganews.com!local-4.nntp.ord.giganews.com!nntp.earthlink.com!news.earthlink.com.POSTED!not-for-mail
NNTP-Posting-Date: Mon, 30 Sep 2024 07:43:16 +0000
Subject: Re: Can't Avoid That Shit Rust - Even On Gentoo
Newsgroups: comp.os.linux.advocacy,comp.os.linux.misc
References: <pan$96411$d204da43$cc34bb91$1fe98651@linux.rocks>
 <5mqdnZuGq4lgwm_7nZ2dnZfqnPSdnZ2d@earthlink.com>
 <9tDIO.25203$afc4.21891@fx42.iad> <llgvjcF5rlhU3@mid.individual.net>
 <59JIO.96321$WtV9.10707@fx10.iad> <vd8bou$15h6g$2@dont-email.me>
 <18udnd3mEtEGfGX7nZ2dnZfqnPGdnZ2d@earthlink.com>
 <vdap5d$1kp35$4@dont-email.me>
 <fcKcnSXE3MsnqWf7nZ2dnZfqnPudnZ2d@earthlink.com>
 <D0rKO.165127$EEm7.5633@fx16.iad> <vddevg$24fps$4@dont-email.me>
 <llv1scFa6uvU1@mid.individual.net>
From: "186282@ud0s4.net" <186283@ud0s4.net>
Organization: wokiesux
Date: Mon, 30 Sep 2024 03:43:16 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <llv1scFa6uvU1@mid.individual.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Message-ID: <D-6cnfCih5UIy2f7nZ2dnZfqn_adnZ2d@earthlink.com>
Lines: 18
X-Usenet-Provider: http://www.giganews.com
NNTP-Posting-Host: 99.101.150.97
X-Trace: sv3-EpIO8EMhif9WUkoly5IpuiC6TQOVHOxGZfVizh584DSz1+j8aKsJhqdQCxJo1lA+Fu+RcTZG0ptZb6k!QSzCjHqMXViq77qp5cU8qIq/fDDy8s45peYgSixAm7CdB4Q4cBi3AXJu1UfLj1J8PwnoEbQ8k9Ec!WpmXaFLrVTF2+RyqDP/p
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
Bytes: 2437

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 ......