Deutsch English Français Italiano |
<9NydnXrV8Ka_IV_6nZ2dnZfqnPWdnZ2d@giganews.com> View for Bookmarking (what is this?) Look up another Usenet article |
Path: news.eternal-september.org!eternal-september.org!feeder3.eternal-september.org!border-2.nntp.ord.giganews.com!nntp.giganews.com!local-3.nntp.ord.giganews.com!Xl.tags.giganews.com!local-4.nntp.ord.giganews.com!news.giganews.com.POSTED!not-for-mail NNTP-Posting-Date: Sat, 01 Mar 2025 07:49:54 +0000 Subject: Re: The joy of FORTRAN Newsgroups: comp.os.linux.misc References: <5mqdnZuGq4lgwm_7nZ2dnZfqnPSdnZ2d@earthlink.com> <vde4b8$268qv$22@dont-email.me> <1396870532.749421730.052473.peter_flass-yahoo.com@news.eternal-september.org> <wrapper-20241001111737@ram.dialup.fu-berlin.de> <vpl5uk$hhk$3@reader1.panix.com> <c4acndn4jJXKwCP6nZ2dnZfqnPSdnZ2d@giganews.com> <1214951717.762291306.657281.peter_flass-yahoo.com@news.eternal-september.org> <gIUvP.1415795$21T3.138928@fx18.iad> <vpp6b0$31cet$2@dont-email.me> <5DWdnXyIYo7er136nZ2dnZfqnPednZ2d@giganews.com> <vppkbv$33b82$6@dont-email.me> <vpqm2d$39d65$1@dont-email.me> <-ducnbYn4JrmyFz6nZ2dnZfqn_idnZ2d@giganews.com> <m2d8haFnv00U2@mid.individual.net> <4rOcnbWnvNi3L1z6nZ2dnZfqn_GdnZ2d@giganews.com> <20250228094215.00001e7e@gmail.com> <vptb92$3r2n0$16@dont-email.me> <20250228141634.0000296d@gmail.com> <vptdeq$3s11n$3@dont-email.me> <20250228153500.00000dd5@gmail.com> <vptt5u$3ud2o$6@dont-email.me> <6D2dnRL30pRfG1_6nZ2dnZfqnPQAAAAA@giganews.com> <m2fiteF3tr0U5@mid.individual.net> From: c186282 <c186282@nnada.net> Date: Sat, 1 Mar 2025 02:49:48 -0500 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: <m2fiteF3tr0U5@mid.individual.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Message-ID: <9NydnXrV8Ka_IV_6nZ2dnZfqnPWdnZ2d@giganews.com> Lines: 69 X-Usenet-Provider: http://www.giganews.com X-Trace: sv3-LaCswU8VV726d0FNgESgcx0TnU7qGITQmhIz6RmXcjkPyV6tSR2re4QtskpYsqwkEKeGxLiZMdjG8Tm!Iwx1S4Zom7/t4AMPs1qoynbmcyrjxl0fGbw0jhkdTPeavfzR2R1wVEG1gkDci/w2bxA5CgfjXRPK X-Complaints-To: abuse@giganews.com X-DMCA-Notifications: http://www.giganews.com/info/dmca.html 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 On 3/1/25 12:05 AM, rbowman wrote: > On Fri, 28 Feb 2025 23:02:07 -0500, c186282 wrote: > >> On 2/28/25 9:59 PM, Lawrence D'Oliveiro wrote: >>> On Fri, 28 Feb 2025 15:35:00 -0800, John Ames wrote: >>> >>>> On Fri, 28 Feb 2025 22:30:51 -0000 (UTC) >>>> Lawrence D'Oliveiro <ldo@nz.invalid> wrote: >>>> >>>>>>> In any piece of Free software, such a limitation would sooner or >>>>>>> later be seen as a bug, and a patch would be available to fix it. >>>>>> >>>>>> Ristretto is ~18 years old by now, and there's still no option to >>>>>> disable its Windows Picture & Fax Viewer-esque "index the whole >>>>>> directory on launch" behavior. There are multiple threads on r/xfce >>>>>> about the performance penalties this imposes when viewing images >>>>>> from large-ish directories. >>>>> >>>>> Obviously nobody cares. At least, nobody with any ability to offer a >>>>> fix. >>>> >>>> So your argument is that all problematic Free Software limitations get >>>> fixed, except for the ones that don't get fixed, which are, ipso >>>> facto, >>>> not problematic, even when they cause well-documented and >>>> oft-discussed problems? >>> >>> I figure, if a problem affects something like 100 people, then one of >>> those 100 would have some programming skills to be able to offer a fix. >> >> >> "Programming skills" ? More like one in 100,000 users. > > > I don't know what Ristretto is but I am familiar with bug fixes, Sometimes > you look at a non-critical problem that affects few users, examine the > possible fixes, realize it is a gigantic black pit filled with IEDs, and > assign it a priority of 5 (which in our system meant 'when hell freezes > over') > > And that is for commercial software that people are paying money for... > One of the problems with skilled programmers is they are adept at sniffing > out rats. There MAY be a near-future fix for this mess - "AI" code analysis/rewrite. Explain the fault and the "AI" can put the equiv of 10k human hours into tracking it down and fixing it - before lunch. Inside 10 years that'll improve to 100k human-equiv hours before lunch. It'll be kind of an uninspired brute-force analysis. However it will be cheap and quick and the "AI" won't unionize or need maternity leave. In 10-15 years humans won't write commercial code at all, you will explain the needs to the "AI" and it'll write it from "Lego"-like modules in some lang made to be EZ for "AI" to work with (but not for humans to understand). It will be reasonably tight code. All those 'C' macros and ultra-compacted unreadable lines some wags create ... stuff we've talked about ... that's gonna be the means and look of the code. Beyond that we've created our own Creature and humans will just be OUT of the software biz except at the highest, most abstract, levels. The 'Jobs-ian' "concept" people will be all that's left - until the "AI" can do that better too.