The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: John Cowan <cowan@ccil.org>
To: Clem Cole <clemc@ccc.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 18:12:56 -0500	[thread overview]
Message-ID: <CAD2gp_S2ENmux1g+NOnR8ZPNx4eAXmP3zaZkYDdCEscusmhVyA@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2NFG+sxPK8QhCiUfRE2OUVk0J4fW90qQ1ONBmYa58q3Xg@mail.gmail.com>

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

On Tue, Feb 1, 2022 at 4:33 PM Clem Cole <clemc@ccc.com> wrote:


> My disagreement with them using scripting (python) as step one is the lack
> of teaching data typing early
>

Teaching types is very important.  But Python is strongly typed: a string
is not a number is not a hashtable.  When it's important for performance
reasons or consistency across a large codebase, you can add static type
information to your Python code without overloading n00b brains with
mandatory type annotations.

AND python's silly use space/tabs to set up structure instead of  real {}
> or B/E blocks.
>

Nobody would accept code that was incorrectly indented (although some
languages have more than one indentation convention, like C) in an
assignment or pull request.  And when looking at correct or mostly correct
code, we look at the indentation structure, not the braces.  That being so,
having both braces and indentation is fundamentally a DRY violation.

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.
>

I think it was a customer revolt that persuaded IBM to add "mixed-mode"
expressions like "A + I" to Fortran IV; they had been disallowed in Fortran
II.  I haven't heard anyone saying we ought to revert that change.

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

  reply	other threads:[~2022-02-01 23:13 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 [this message]
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=CAD2gp_S2ENmux1g+NOnR8ZPNx4eAXmP3zaZkYDdCEscusmhVyA@mail.gmail.com \
    --to=cowan@ccil.org \
    --cc=clemc@ccc.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).