Deutsch   English   Français   Italiano  
<vdpi96$bgk6$7@dont-email.me>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.os.linux.misc,alt.folklore.computers
Subject: Re: The joy of FORTRAN
Date: Fri, 4 Oct 2024 20:13:27 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 21
Message-ID: <vdpi96$bgk6$7@dont-email.me>
References: <pan$96411$d204da43$cc34bb91$1fe98651@linux.rocks>
	<5mqdnZuGq4lgwm_7nZ2dnZfqnPSdnZ2d@earthlink.com>
	<vcub5c$36h63$1@dont-email.me>
	<36KdnVlGJu9VLW77nZ2dnZfqn_qdnZ2d@earthlink.com>
	<IfZIO.214180$FzW1.122138@fx14.iad>
	<ZLecncKpCfSfT2n7nZ2dnZfqnPudnZ2d@earthlink.com>
	<ZOfJO.194439$kxD8.179224@fx11.iad> <vd4hgd$c3jf$8@dont-email.me>
	<AxicncFTKaRW52L7nZ2dnZfqnPednZ2d@earthlink.com>
	<vdnvk0$49ai$2@dont-email.me>
	<o8icnRRnt4ChGGL7nZ2dnZfqn_idnZ2d@earthlink.com>
	<vdo3j6$4q92$1@dont-email.me> <lm9kg6Ft2vgU2@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Fri, 04 Oct 2024 22:13:27 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="53e6a1f358fb9450cb41203dd8d281a9";
	logging-data="377478"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/qLuqNQfRqmqJlzlXhQPZK"
User-Agent: Pan/0.160 (Toresk; )
Cancel-Lock: sha1:Wa+gEVn6+3owqz3jJX3yxstZjcQ=
Bytes: 2383

On 4 Oct 2024 07:40:54 GMT, rbowman wrote:

> On Fri, 4 Oct 2024 06:56:38 -0000 (UTC), Lawrence D'Oliveiro wrote:
> 
>> But C = “machine language” under the hood. That’s what Python uses.
> 
> It's turtles, turtles, turtles all the way down...

One thing we learned in Comp Sci was the concept of “abstract machines”. 
There is no fundamental difference between hardware and software: 
“hardware” is just what you start with when you turn the power on, but 
does that include “firmware” and “microcode”?

A lot of what we do in programming/scripting is building one layer of 
“abstract machine” on top of another, until we get to something optimized 
for solving our particular problem.

Of course, all this goes out the window once you get to the GUI layer; 
that is the end of the line, with no more programmability (easily) 
possible on top of that. From that point on, the human user has to do all 
the work.