Path: csiph.com!1.us.feeder.erje.net!feeder.erje.net!border1.nntp.dca1.giganews.com!nntp.giganews.com!buffer1.nntp.dca1.giganews.com!buffer2.nntp.dca1.giganews.com!nntp.earthlink.com!news.earthlink.com.POSTED!not-for-mail NNTP-Posting-Date: Sat, 16 Jul 2022 22:47:50 -0500 Subject: Re: Fwd: Linux on a small memory PC Newsgroups: comp.os.linux.misc References: <871quvs7m8.fsf@usenet.ankman.de> <87sfn8pr5t.fsf@usenet.ankman.de> <87zghai2dh.fsf@usenet.ankman.de> <16ydncnktcv0sE__nZ2dnUU7-Q3NnZ2d@earthlink.com> From: "25B.Z959" <25B.Z959@nada.net> Date: Sat, 16 Jul 2022 23:47:48 -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: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Message-ID: Lines: 70 X-Usenet-Provider: http://www.giganews.com NNTP-Posting-Host: 98.77.165.113 X-Trace: sv3-bMunmkxyp+rQawrPNSIsPS0ctygvQazctbwybhfQmCEMwEJF9HZLctUF9+tiAOT18JwDp7+NdnX80wy!vBB/8W6C4iq1ZssAoada7Mgs9GuYey/kW8qE2NM4yrKdZfM6ozkFPX3uocSljOd1WgP2tQPb7j28!Ctg//7a7ntz7UcNGvP8H 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 X-Original-Bytes: 3852 Xref: csiph.com comp.os.linux.misc:35059 On 7/16/22 8:48 AM, Dan Espen wrote: > "25B.Z959" <25B.Z959@nada.net> writes: > >> On 7/15/22 3:48 PM, Andreas Kohlbach wrote: >>> On Thu, 14 Jul 2022 20:16:57 -0400, 25B.Z959 wrote: >>>> >>>> On 7/10/22 5:57 PM, Andreas Kohlbach wrote: >>>>> On Sun, 10 Jul 2022 00:45:42 -0400, 25B.Z959 wrote: >>>>>> >>>>>> Oh well, almost 80 years before we have THAT problem >>>>>> again ..... >>>>> 2000 - 80 = 1920 ? >>>>> 2038 - 80 = 1958 ? >>>>> The Y2K38 problem sends clocks back about 137 years. >>>>> I have no idea what you mean. >>>> >>>> I lost you there .... >>> What were you referring to with "almost 80 years before"? >> >> >> That's it's about 80 years until THIS decades 2-digit >> dates become a problem ... >> >> Fortunately, few are so cheap to be using 2-digit dates >> anymore. Not so in the past - they just assumed 19xx. >> Saved a little space, easier calx. > > There you go, true to form. Now people use 2 digit dates because they > are cheap. You are neglecting Computers Past ..... low speed, low capacity. You simplified calx, you squeezed-down the data anywhere you could. I know, I had to do it. So yes, they DID intentionally skimp. > Hey, I'm writing dates in the US format mm/dd/yy. Why? Because the > context makes it very clear what those 2 digits represent. Until 'yy' doesn't mean "20yy" anymore. > For data that covers shorter time spans, 2 digits is the way to go. > Comparing 2 digit dates, knowing where we are in the current century is > trivially easy. > > There are many cases where using 2 digit dates makes a lot of sense. > It has nothing to do with anyone being cheap. Human lifespans now fairly often exceed 100 years. There MAY even be a very few alive now born in the 1800s. There WILL be a great many in 2100 born in the 1900s. Not just people either, laws, financial agreements, contracts etc.. So two-digits does NOT cover it. Don't be cheap ... unix epoch at the very least. You can skip the decimal points. Hey, you can always use Roman numerals - you can easily squeeze two standard ASCII chars into a single byte ... even THREE bits if 000=I, 001=V, 010=L, 011=X, 100=C, 101=M and 110=negative. Easy to write a 'C' pgm using odd-sized bit-fields so nothing's wasted :-) I've done enough microcontroller programs ... you SQUEEZE !