The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Paul Winalski <paul.winalski@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Happy birthday, John Backus!
Date: Mon, 3 Dec 2018 15:37:04 -0500	[thread overview]
Message-ID: <CAC20D2MPZY-D9PqJrYU1W5FrRWa_fo1xutAeaXZgkZ4dOkmexg@mail.gmail.com> (raw)
In-Reply-To: <CABH=_VTGj_Fugj7nNPu47G2nP2kjJivw-ummrWYnQe8tRtwqkQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1685 bytes --]

On Mon, Dec 3, 2018 at 3:21 PM Paul Winalski <paul.winalski@gmail.com>
wrote:

> Fortran was being devised at the same time that Chomsky, et.
> al. were doing the research on formal languages.  Essentially, Fortran
> syntax was devised before computer scientists knew better.  I suspect
> COBOL has similar issues.
>
I agree.  I think you nailed about "not knowing any better.'   And it
really is amazing how well it has endured.  Like a lot of things, the first
guys do make errors because they really have not yet eccounter the longer
term issues - they are just trying to solve the problem they had in front
of them.  On another fron, just think the issues in networking that were
made in the 70s.  Same thing.   But IP/TCP works and works really well and
has endured.

You folks in the compiler team and in particular the Fortran crew, did a
great job over the years.   I used to kid your boss asking of there were
Fortran developers than customers in our DEC days; but all kidding aside. And
he knew I knew.  I have always respected those folks.   As I said, they
paid my salary for so many years.

I think it's sad we don't teach Fortran to 'modern' programmers in a
comparitive languages class.   The students should know what is good, why
it has lasted and marvel at what a wonder system people devised in the late
1950s and how well Computer Scientists have over the next 60 years kept it
strong and relevant.  Then you can teach them, Rust, Go or whatever the
cool kids think are hot and important.    Ask them all, why do we think
this languages will or will not last (and the end, it will be economics but
that's another thread).

Clem
ᐧ

[-- Attachment #2: Type: text/html, Size: 3568 bytes --]

  reply	other threads:[~2018-12-03 20:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-02 22:17 Dave Horsfall
2018-12-02 22:34 ` Toby Thain
2018-12-03  1:32   ` Rob Pike
2018-12-03  4:11     ` Toby Thain
2018-12-03  4:27       ` Rob Pike
2018-12-03 13:10         ` John P. Linderman
2018-12-03 22:44           ` ron
2018-12-03 16:25 ` Clem Cole
2018-12-03 20:20   ` Paul Winalski
2018-12-03 20:37     ` Clem Cole [this message]
2018-12-03 20:46     ` Hellwig Geisse
2018-12-03 22:24   ` Paul Winalski
2018-12-03 23:00     ` Lawrence Stewart
2018-12-04 11:53   ` Tony Finch
2018-12-04 14:23     ` Clem Cole
2018-12-04 14:43 Noel Chiappa
2018-12-04 14:53 ` Clem Cole
2018-12-04 16:24   ` Tim Rylance
2018-12-04 16:53     ` Clem Cole
2018-12-04 17:46       ` Paul Winalski
2018-12-04 20:59         ` Paul Winalski
2018-12-05 17:49         ` Paul Winalski
2018-12-04 15:18 ` Toby Thain

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAC20D2MPZY-D9PqJrYU1W5FrRWa_fo1xutAeaXZgkZ4dOkmexg@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=paul.winalski@gmail.com \
    --cc=tuhs@tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).