The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ron@ronnatalie.com (Ronald Natalie)
Subject: [TUHS] Origin year of BSD csh?
Date: Mon, 27 Jun 2016 16:28:14 -0500	[thread overview]
Message-ID: <E69B1487-94B8-49C6-BA11-0F9FEEABE623@ronnatalie.com> (raw)
In-Reply-To: <20160627212028.GH3353@mercury.ccil.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1367 bytes --]

Hard to believe the 8086 chip was “optimized” for anything.  The instruction set was designed for programming terminals.
The iapx32 was designed to run higher level languages (Ada) but despite how “nicely” it implemented this, it couldn’t counter the fact that it was molasses slow doing anything.   It was easier to build craftier compilers than trying to burn the smarts into silicon.

> On Jun 27, 2016, at 4:20 PM, John Cowan <cowan at mercury.ccil.org> wrote:
> 
> Ronald Natalie scripsit:
> 
>> Sure, it was a long time ago, but I’ll tell you what I remember.
>> The one thing I do remember is that the SV /bin/sh was written in
>> these horrendous macros that sort of made it look like algol or
>> something.
> 
> I've always wondered what would have happened if Algol 68 (brought back
> from England by Bourne) had out-competed C at Bell Labs, and had become
> the dominant programming language of Unix.  Probably the commercial
> world would have standardized on Pascal, something that almost happened
> (the x86 chip is optimized for Pascal in several ways).
> 
> -- 
> John Cowan          http://www.ccil.org/~cowan        cowan at ccil.org
> "But I am the real Strider, fortunately," he said, looking down at them
> with his face softened by a sudden smile.  "I am Aragorn son of Arathorn,
> and if by life or death I can save you, I will."



  reply	other threads:[~2016-06-27 21:28 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-26 10:14 Aharon Robbins
2016-06-26 16:30 ` Mary Ann Horton
2016-06-26 18:14   ` Larry McVoy
2016-06-26 18:32     ` Ronald Natalie
2016-06-26 20:43       ` John Cowan
2016-06-27  0:59         ` Larry McVoy
2016-06-27  1:11           ` John Cowan
2016-06-27 11:27       ` Sven Mascheck
2016-06-27 12:47         ` Steve Nickolas
2016-06-27 14:58         ` Joerg Schilling
2016-06-27 15:29           ` Ronald Natalie
2016-06-27 16:22         ` John Cowan
2016-06-27 16:35           ` Steve Nickolas
2016-06-27 20:00         ` Dave Horsfall
2016-06-27 20:33         ` Ronald Natalie
2016-06-27 20:44           ` Clem Cole
2016-06-27 21:02           ` Steve Nickolas
2016-06-27 21:15             ` Ronald Natalie
2016-06-27 21:20           ` John Cowan
2016-06-27 21:28             ` Ronald Natalie [this message]
2016-06-27 21:45               ` John Cowan
2016-06-28  6:49               ` Peter Jeremy
2016-06-28  7:51                 ` arnold
2016-06-27 21:29           ` Random832
2016-06-28 14:47         ` Tony Finch
2016-06-26 19:41     ` Clem Cole
2016-06-27 10:31       ` Joerg Schilling
2016-06-27 13:01         ` Ronald Natalie
2016-06-27 13:15           ` Steffen Nurpmeso
2016-06-27 15:17           ` Joerg Schilling
2016-06-27 13:39         ` [TUHS] Bizarre job control, was csh Warren Toomey
2016-06-27 15:00           ` Steve Nickolas
2016-06-27 15:13             ` Joerg Schilling
2016-06-27 15:23               ` Steve Nickolas
2016-06-26 20:58     ` [TUHS] Origin year of BSD csh? Steve Nickolas
2016-06-27 10:03 ` Joerg Schilling

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=E69B1487-94B8-49C6-BA11-0F9FEEABE623@ronnatalie.com \
    --to=ron@ronnatalie.com \
    /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).