Path: ...!news.nobody.at!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: candycanearter07 <candycanearter07@candycanearter07.nomail.afraid>
Newsgroups: comp.os.linux.advocacy,comp.os.linux.misc
Subject: Re: Can't Avoid That Shit Rust - Even On Gentoo
Date: Mon, 30 Sep 2024 19:40:06 -0000 (UTC)
Organization: the-candyden-of-code
Lines: 24
Message-ID: <slrnvflggs.lr8.candycanearter07@candydeb.host.invalid>
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>
 <D-6cnfCih5UIy2f7nZ2dnZfqn_adnZ2d@earthlink.com>
Injection-Date: Mon, 30 Sep 2024 21:40:06 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="5684a4d30402052661823de0cd13dd98";
	logging-data="2493472"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18cpP+30StPRZRRDTHeQ30k7tsZbDfo63dP2IS1GtLY1g=="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:Rht0fWOn24npeykqagi0G6fmIcA=
X-Face: b{dPmN&%4|lEo,wUO\"KLEOu5N_br(N2Yuc5/qcR5i>9-!^e\.Tw9?/m0}/~:UOM:Zf]%
 b+ V4R8q|QiU/R8\|G\WpC`-s?=)\fbtNc&=/a3a)r7xbRI]Vl)r<%PTriJ3pGpl_/B6!8pe\btzx
 `~R! r3.0#lHRE+^Gro0[cjsban'vZ#j7,?I/tHk{s=TFJ:H?~=]`O*~3ZX`qik`b:.gVIc-[$t/e
 ZrQsWJ >|l^I_[pbsIqwoz.WGA]<D
Bytes: 2760

186282@ud0s4.net <186283@ud0s4.net> wrote at 07:43 this Monday (GMT):
> 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 ......


Then, people ignore the problem until it's right there.
For instance, the 2038 problem I'm betting will be ignored until 2035.
-- 
user <candycane> is generated from /dev/urandom