Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: John Ames <commodorejohn@gmail.com>
Newsgroups: comp.os.linux.misc,comp.os.linux.advocacy
Subject: Re: GIMP 3.0.0-RC1
Date: Thu, 13 Feb 2025 08:03:00 -0800
Organization: A noiseless patient Spider
Lines: 25
Message-ID: <20250213080300.00001d26@gmail.com>
References: <vkjmdg$30kff$1@dont-email.me>
	<c686fb74-4fac-0809-7005-417c76ee0e3b@example.net>
	<nbReP.633803$oR74.271654@fx16.iad>
	<NnVeP.44028$vfee.11890@fx45.iad>
	<vo6ubb$3ue2q$2@dont-email.me>
	<RhOdnY5Kb8vulDr6nZ2dnZfqnPudnZ2d@earthlink.com>
	<vo7lp6$25uo$2@dont-email.me>
	<655acbf6-05e5-69ff-8a44-9f7075aafa2e@example.net>
	<ddNpP.567620$iNI.244105@fx14.iad>
	<m0pqs3ForauU2@mid.individual.net>
	<g9qcnUmy1pxdrTX6nZ2dnZfqnPqdnZ2d@earthlink.com>
	<m0r59mFrbnU1@mid.individual.net>
	<yn0qP.587031$iNI.359829@fx14.iad>
	<VtWdnaJY5fz99zT6nZ2dnZfqnPudnZ2d@earthlink.com>
	<20250210093054.00001375@gmail.com>
	<vofgo6$1p8fn$1@dont-email.me>
	<KwSdnd_yRPwhvjH6nZ2dnZfqnPidnZ2d@earthlink.com>
	<20250212081704.00003ce1@gmail.com>
	<slrnvqq09r.38buj.candycanearter07@candydeb.host.invalid>
	<DKOcnSWcJP6OgTD6nZ2dnZfqnPqdnZ2d@earthlink.com>
	<20250212145430.00001040@gmail.com>
	<vojqqp$2klsq$2@dont-email.me>
	<6fqdnVeJects6jD6nZ2dnZfqn_GdnZ2d@earthlink.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 13 Feb 2025 17:03:04 +0100 (CET)
Injection-Info: dont-email.me; posting-host="24704e308c6098bc3c3df94bf98cfc0e";
	logging-data="3118761"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/SU2MQS7jt5X3YBDoRFxDwnLyvT2+Rrms="
Cancel-Lock: sha1:jMaHzOA31zrV65pxtCm54bh1Cxo=
X-Newsreader: Claws Mail 4.3.0 (GTK 3.24.42; x86_64-w64-mingw32)
Bytes: 3262

On Wed, 12 Feb 2025 23:41:23 -0500
"WokieSux282@ud0s4.net" <WokieSux283@ud0s4.net> wrote:

> As for including type info - limits and more - the effective overhead
> in these days of gigabit flow and GHz multicore chips is negligible.
> As such I'd say to include it one way or another.

Again, if you want to argue for the safety of enforced bounds-checking
being worth the trade-off in performance, I'm willing to entertain that
argument, even if I only situationally agree. Lots of languages have
chosen to make that trade, and more power to 'em.

But what remains absolutely - and, AFAIK, uniquely - *demented* is for
a language to specify that *two arrays of different sizes are different
types of entity,* even if their elements are identically-typed.

There is *no* reason that I can see to do this. A language that forgoes
bounds-checking entirely gains some performance, at the cost of safety;
a language that includes bounds info as part of the array's structure
gains safety and convenience at the cost of some performance. Pascal,
on the other hand, gets no performance advantage, while burdening the
programmer with all the bookkeeping that is *necessary* for safety in
languages like C, even though it keeps all the information needed to
provide a less burdensome, more convenient alternative. Truly deranged.