The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Dan Cross <crossd@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>,
	Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: [TUHS] ratfor vibe
Date: Tue, 1 Feb 2022 16:33:19 -0500	[thread overview]
Message-ID: <CAC20D2NFG+sxPK8QhCiUfRE2OUVk0J4fW90qQ1ONBmYa58q3Xg@mail.gmail.com> (raw)
In-Reply-To: <CAEoi9W4upTAXRmhL_w_xK63Dn4KAKOK6ikK9tZa-tD0LZh4a5Q@mail.gmail.com>

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

On Tue, Feb 1, 2022 at 4:22 PM Dan Cross <crossd@gmail.com> wrote:

> On Tue, Feb 1, 2022 at 2:40 PM Clem Cole <clemc@ccc.com> wrote:
>
>> Dan - thanks.
>>
>
> Sure thing.
>
> By the way: the thing I was thinking about earlier that was so biting
> towards OOP was an earlier version of Harper's post, in which he writes,
> "Object-oriented programming is eliminated entirely from the introductory
> curriculum, because it is both anti-modular and anti-parallel by its very
> nature, and hence unsuitable for a modern CS curriculum."
> https://web.archive.org/web/20110321004746/https://existentialtype.wordpress.com/2011/03/15/teaching-fp-to-freshmen/
> (How's _that_ for an academic glove-slap?)
>
Amen...

My disagreement with them using scripting (python) as step one is the lack
of teaching data typing early AND python's silly use space/tabs to set up
structure instead of  real {} or B/E blocks.  Automatic data conversion has
never been a good idea in my experience because like many things that
happen magically, it almost never works as I expect.

Funny we were discussing the roff family and that is why I like it over
things like Word -- way too much hidden behind the screen for my taste.
I'm a make it explicit kinda guy I guess.  I hate surprises ...

Also, it remains to be seen if teaching FP early helps - which they are
clearly making play.  Who am I to say, as one of the earliest languages I
learned APL, so FP thinking was drilled into me in my youth.

Clem

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

  reply	other threads:[~2022-02-01 21:34 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 [this message]
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
  -- 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=CAC20D2NFG+sxPK8QhCiUfRE2OUVk0J4fW90qQ1ONBmYa58q3Xg@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=crossd@gmail.com \
    --cc=jnc@mercury.lcs.mit.edu \
    --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).