The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] PDP-11 legacy, C, and modern architectures
Date: Wed, 27 Jun 2018 10:38:46 -0400	[thread overview]
Message-ID: <CAC20D2Oy1-JymrniBdZgjGoX0Gei4VzMTupH+yjSX6WVLdpS_w@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2P6LcfP9HD6VrmGH35NkUL873h51ZJLs5HABB1B2ygADg@mail.gmail.com>

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

I need to get a keyboard who keys don't stick.... sigh....  Clem
ᐧ

On Wed, Jun 27, 2018 at 10:33 AM, Clem Cole <clemc@ccc.com> wrote:

> I guess my take on it is mixed.   I see some of his points but over all I
> disagree with most of them.  I firmly believe if you look at anything long
> enough you will find flaws.  There is no perfect.   I think Fortran, C,
> even Algol are credits for more what people were able to think about at the
> time and how well they lasted.   As I have said in other places, Fortran is
> not going away. Clem Cole's answer is the Future of Fortran Programming
> Dead
> <https://www.quora.com/Is-the-future-of-Fortran-programming-dead/answer/Clem-Cole> also
> applies to C.   It's just not broken and he's wrong.   Go, Rust *et al*
> is not going to magically overtake C, just as Fortran as not been displaced
> in my lifetime (BTW, I >>like<< both Go and Rust and think they are
> interesting new languages).   He thinks C is not long a low level language
> because when Ken abstracted the PDP-7 into B and then Dennis abstracted the
> PDP-11 into C, the systems were simple.  The HW designers are in a giant
> fake out at this point, so things that used to work like 'register' no
> longer make sense.  Now its the compiler that binds to the primitives
> available to the functions under the covers and there is more to use than
> the PDP-11 and PDP-7 offered.    But wait, that is not always true.   So I
> think he's wrong.   I think you leave the language alone and if the HW
> moves on great.   But if we have a simple system like you have on the Amtel
> chips that most Arduino's and lots of other embedded C programs use, C is
> very low level and most his arguments go away.
>
> Cken
> ᐧ
>

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

  reply	other threads:[~2018-06-27 14:39 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-26 17:54 Nelson H. F. Beebe
2018-06-26 18:03 ` Cornelius Keck
2018-06-26 21:21   ` Nelson H. F. Beebe
2018-06-26 21:56   ` Kurt H Maier
2018-06-26 18:52 ` Ronald Natalie
2018-06-26 19:01 ` Ronald Natalie
2018-06-26 21:16   ` Arthur Krewat
2018-06-26 21:50     ` Larry McVoy
2018-06-26 21:54       ` Ronald Natalie
2018-06-26 21:59         ` Larry McVoy
2018-06-26 22:20           ` Bakul Shah
2018-06-26 22:33             ` Arthur Krewat
2018-06-26 23:53               ` Bakul Shah
2018-06-27  8:30             ` Tim Bradshaw
2018-06-26 22:33           ` Andy Kosela
2018-06-27  0:11             ` Bakul Shah
2018-06-27  6:10               ` arnold
2018-06-27  2:18           ` [TUHS] PDP-11 legacy, C, and modern architectTures Theodore Y. Ts'o
2018-06-27  2:22             ` Theodore Y. Ts'o
2018-06-28 14:36             ` Steffen Nurpmeso
2018-06-27 11:26         ` [TUHS] PDP-11 legacy, C, and modern architectures Tony Finch
2018-06-27 14:33           ` Clem Cole
2018-06-27 14:38             ` Clem Cole [this message]
2018-06-27 15:30             ` Paul Winalski
2018-06-27 16:55               ` Tim Bradshaw
2018-06-27  6:27     ` arnold
2018-06-27 16:00 ` Steve Johnson
2018-06-28  4:12   ` Bakul Shah
2018-06-28 14:15     ` Theodore Y. Ts'o
2018-06-28 14:40       ` Larry McVoy
2018-06-28 14:55         ` Perry E. Metzger
2018-06-28 14:58           ` Larry McVoy
2018-06-28 15:39             ` Tim Bradshaw
2018-06-28 16:02               ` Larry McVoy
2018-06-28 16:41                 ` Tim Bradshaw
2018-06-28 16:59                   ` Paul Winalski
2018-06-28 17:09                   ` Larry McVoy
2018-06-29 15:32                     ` tfb
2018-06-29 16:09                       ` Perry E. Metzger
2018-06-29 17:51                       ` Larry McVoy
2018-06-29 18:27                         ` Tim Bradshaw
2018-06-29 19:02                         ` Perry E. Metzger
2018-06-28 20:37                 ` Perry E. Metzger
2018-06-28 15:37         ` Clem Cole
2018-06-28 20:37           ` Lawrence Stewart
2018-06-28 14:43       ` Perry E. Metzger
2018-06-28 14:56         ` Larry McVoy
2018-06-28 15:07           ` Warner Losh
2018-06-28 19:42           ` Perry E. Metzger
2018-06-28 19:55             ` Paul Winalski
2018-06-28 20:42             ` Warner Losh
2018-06-28 21:03               ` Perry E. Metzger
2018-06-28 22:29                 ` Theodore Y. Ts'o
2018-06-29  0:18                   ` Larry McVoy
2018-06-29 15:41                     ` Perry E. Metzger
2018-06-29 18:01                       ` Larry McVoy
2018-06-29 19:07                         ` Perry E. Metzger
2018-06-29  5:58                   ` Michael Kjörling
2018-06-28 20:52             ` Lawrence Stewart
2018-06-28 21:07               ` Perry E. Metzger
2018-06-28 16:45       ` Paul Winalski
2018-06-28 20:47         ` Perry E. Metzger
2018-06-29 15:43         ` emanuel stiebler
2018-06-29  2:02       ` Bakul Shah
2018-06-29 12:58         ` Theodore Y. Ts'o
2018-06-29 18:41           ` Perry E. Metzger
2018-06-29  1:02 Noel Chiappa
2018-06-29  1:06 Noel Chiappa

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=CAC20D2Oy1-JymrniBdZgjGoX0Gei4VzMTupH+yjSX6WVLdpS_w@mail.gmail.com \
    --to=clemc@ccc.com \
    --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).