The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Win Treese <treese@acm.org>
To: The Unix Heritage Society <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] ratfor vibe
Date: Tue, 1 Feb 2022 16:50:49 -0500	[thread overview]
Message-ID: <65068AA0-BFEF-46B8-9068-2A24039371D3@acm.org> (raw)
In-Reply-To: <20220201181909.6224518C086@mercury.lcs.mit.edu>


> On Feb 1, 2022, at 1:19 PM, Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
> 
>> From: Clem Cole
> 
>> So by the late 70s/early 80s, [except for MIT where LISP/Scheme reigned]
> 
> Not quite. The picture is complicated, because outside the EECS department,
> they all did their own thing - e.g. in the mid-70's I took a programming
> intro couse in the Civil Engineering department which used Fortran. But in
> EECS, in the mid-70's, their intro programming course used assembler
> (PDP-11), Algol, and LISP - very roughly, a third of the time in each. Later
> on, I think it used CLU (hey, that was MIT-grown :-). I think Scheme was used
> later. In both of these cases, I have no idea if it was _only_ CLU/Scheme, or
> if they did part of it in other languages.

I took 6.001 (with Scheme) in the spring of 1983, which was using a course
handout version of what became Structure and Interpretation of Computer
Programs by Sussman and Abelson. My impression was that it had been
around for a year before that, but not much more, and it was part of
revamping the EECS core curriculum at the time.

In at least the early 80s, CLU was used in 6.170, Software Engineering
Laboratory, in which a big project was writing a compiler.

And Fortran was still being taught for the other engineering departments.
In 1982(ish), those departments had the Joint Computing Facility for a lot
of their computing, of which the star then was a new VAX 11/782.

- Win


  parent reply	other threads:[~2022-02-01 21:56 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01 18:19 Noel Chiappa
2022-02-01 18:47 ` Clem Cole
2022-02-01 19:10   ` Dan Cross
2022-02-01 19:39     ` Clem Cole
2022-02-01 21:21       ` Dan Cross
2022-02-01 21:33         ` Clem Cole
2022-02-01 23:12           ` John Cowan
2022-02-01 19:39   ` Richard Salz
2022-02-01 22:30   ` Erik E. Fair
2022-02-02  0:54     ` Yeechang Lee
2022-02-01 21:50 ` Win Treese [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-01-31 20:46 Will Senn
2022-02-01 15:37 ` arnold
2022-02-01 15:52   ` Ralph Corderoy
2022-02-01 16:58     ` Clem Cole
2022-02-01 17:02     ` silas poulson
2022-02-02  7:47     ` arnold
2022-02-03 18:57       ` silas poulson
2022-02-04  8:26         ` arnold
2022-02-04 19:41           ` John Cowan
2022-02-10 15:18       ` Ralph Corderoy
2022-02-03  4:00 ` Will Senn
2022-02-03  4:31   ` Al Kossow
2022-02-03  5:16     ` Warner Losh
2022-02-03 20:00   ` Adam Thornton
2022-02-04  6:06     ` Ori Idan
2022-02-04 17:35       ` Adam Thornton
2022-02-04 17:44         ` Will Senn

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=65068AA0-BFEF-46B8-9068-2A24039371D3@acm.org \
    --to=treese@acm.org \
    --cc=tuhs@minnie.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).