The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@iitbombay.org>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: [TUHS]: C dialects (was: I can't drive 55: "GOTO considered harmful" 55th anniversary)
Date: Thu, 16 Mar 2023 15:50:42 -0700	[thread overview]
Message-ID: <142EE114-4273-4DE9-A533-F3C08F5E1D26@iitbombay.org> (raw)
In-Reply-To: <20230315035930.C68E018C080@mercury.lcs.mit.edu>

On Mar 14, 2023, at 8:59 PM, Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
> 
>> From: Bakul Shah
> 
>> In hindsight Algol68 may have been the last committee designed language
>> that was good.
> 
> I do not grant your basic assertion. Hoare had it right: "ALGOL 60 [was] a
> language so far ahead of its time that it was not only an improvement on its
> predecessors but also on nearly all its successors." That would definitely
> include Algol68, which was a classic committee-designed nightmare.

You have to realize that even top-notch computer scientists
like Hoare, Dijkstra are/were still people just like us
and have their own biases! And the context matters.

The a68 fights were before my time. I learned about it at grad
school on my own and at the time I had no preconceptions about
it (or for that matter any other language).  Reading the
Algol68 Revised Report was hard but all became clear when I
read an introductory book by Brailsford and Walker, and
another by Pagan. I liked a68's uniform syntax and semantics
very much, in spite of surface syntax issues like DO .. OD. I
just think it got a very bad rap due to personalities, the
language of report itself, the strong opinions of its language
committee, the state of art computers at the time etc. etc.
Today it seems like a smaller language than today's C++, Rust,
Swift etc. If I were to write as many lines of code in it as I
have in C++, possibly I may dislike it but probably not as
much as C++.

Cowan made a point that CL is a committee designed language
that is "not a nightmare". I agree. I missed noting that.


  parent reply	other threads:[~2023-03-16 22:51 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15  3:59 Noel Chiappa
2023-03-15  4:33 ` John Cowan
2023-03-16 22:50 ` Bakul Shah [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-10 11:37 [TUHS] Re: I can't drive 55: "GOTO considered harmful" 55th anniversary Noel Chiappa
2023-03-10 15:54 ` Dan Cross
2023-03-12  7:39   ` Anthony Martin
2023-03-12 11:40     ` Dan Cross
2023-03-13  3:25       ` John Cowan
2023-03-13 10:40         ` Alejandro Colomar (man-pages)
2023-03-13 12:19           ` Dan Cross
2023-03-13 12:43             ` [TUHS] [TUHS]: C dialects (was: I can't drive 55: "GOTO considered harmful" 55th anniversary) Alejandro Colomar
2023-03-13 12:46               ` [TUHS] " Dan Cross
2023-03-13 16:00               ` Paul Winalski
2023-03-13 19:00                 ` Clem Cole
2023-03-13 19:09                   ` Larry McVoy
2023-03-13 19:17                   ` Steve Nickolas
2023-03-13 20:26                     ` Dan Cross
2023-03-13 22:25                       ` Alejandro Colomar (man-pages)
2023-03-13 20:48                   ` Paul Winalski
2023-03-13 20:56                     ` Bakul Shah
2023-03-14  1:06                     ` Larry McVoy
2023-03-13 21:00                   ` Paul Winalski
2023-03-13 21:07                     ` Bakul Shah
2023-03-13 21:14                       ` Dan Cross
2023-03-13 22:15                         ` Dave Horsfall
2023-03-13 22:47                           ` Dave Horsfall
2023-03-14  0:23                             ` Dan Cross
2023-03-14  0:21                           ` Dan Cross
2023-03-14 13:52                             ` Chet Ramey
2023-03-14  1:27                         ` Bakul Shah
2023-03-13 21:28                       ` Paul Winalski
2023-03-14  0:38                     ` John Cowan
2023-03-14  2:49                 ` Theodore Ts'o
2023-03-14  3:06                   ` G. Branden Robinson

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=142EE114-4273-4DE9-A533-F3C08F5E1D26@iitbombay.org \
    --to=bakul@iitbombay.org \
    --cc=jnc@mercury.lcs.mit.edu \
    --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).