The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: dds@aueb.gr (Diomidis Spinellis)
Subject: [TUHS] Algol68 vs. C at Bell Labs
Date: Thu, 30 Jun 2016 22:21:27 +0300	[thread overview]
Message-ID: <2c674075-db86-827b-fd97-30921757e9ae@aueb.gr> (raw)
In-Reply-To: <CAEoi9W5RA0Eb90YT5t_23Q8bwj_Hi8pfmzsNpE0ujWLH-GnC6Q@mail.gmail.com>

On 30/06/2016 18:32, Dan Cross wrote:
> Of
> course it's only of historical interest now, but from a technology
> standpoint MC68000 vs Intel 8088 seems like a no-brainer: the 68k is the
> superior chip.

Two factors might had made the choice of 8088 a more practical one for IBM.

First, the 8088 was a 16-bit CPU with an 8-bit data bus in a cheap 
40-pin package.  This halved the number DRAM chips required and allowed 
the IBM PC to be easily designed along existing easily-available 8-bit 
peripherals.  In contrast the 68000 had a 16-bit data bus in a more 
expensive 64-pin package.  Remember that in the 1980s glue logic was 
implemented through simple TTL chips, so adopting the 68000 might have 
doubled the number of chips on the motherboard.

In addition, the 8086 architecture was an extension of the 8080 one, 
which made it easier to make the MS-DOS API compatible with the CP/M 
one, which was used by many popular programs.  This would simplify their 
porting.  (A lot of early IBM PC software was written in assembly 
language.)  The MS-DOS 1.0 interrupts (system calls) even used the same 
numbers and structures (file control blocks - FCBs) as those used by 
CP/M.  MS-DOS 2.0 added file paths and other Unix-influenced abstractions.



  parent reply	other threads:[~2016-06-30 19:21 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29 15:17 scj
2016-06-30  5:06 ` Dave Horsfall
2016-06-30  5:08 ` John Cowan
2016-06-30 11:18 ` arnold
2016-06-30 11:45   ` arnold
2016-06-30 13:22 ` Clem Cole
2016-06-30 14:05   ` Marc Rochkind
2016-06-30 14:33     ` William Cheswick
2016-06-30 14:43       ` Ronald Natalie
2016-06-30 14:57       ` Joerg Schilling
2016-06-30 15:07         ` Ori Idan
2016-06-30 23:07           ` Dave Horsfall
2016-07-01  3:27           ` Jesus Cea
2016-06-30 15:32     ` Dan Cross
2016-06-30 15:49       ` Larry McVoy
2016-06-30 16:32         ` Clem Cole
2016-07-04  5:08         ` [TUHS] OS for IBM PC (was: Algol68 vs. C at Bell Labs) Greg 'groggy' Lehey
2016-06-30 17:07       ` [TUHS] Algol68 vs. C at Bell Labs John Cowan
2016-06-30 17:57         ` Marc Rochkind
2016-06-30 18:31           ` Dan Cross
2016-06-30 19:21             ` Clem Cole
2016-06-30 19:51               ` Dan Cross
2016-06-30 19:55                 ` Clem Cole
2016-06-30 20:04                   ` Dan Cross
2016-06-30 18:26         ` Steve Nickolas
2016-06-30 19:21       ` Diomidis Spinellis [this message]
2016-06-30 19:43         ` Dan Cross
2016-06-30 19:53           ` Clem Cole
2016-06-30 19:47         ` Clem Cole
2016-06-30 20:57         ` Nemo
2016-06-30 23:11           ` Random832
2016-06-30 23:16           ` Marc Rochkind
2016-06-30 23:38             ` Random832
2016-07-01  0:38             ` Clem Cole
2016-07-01  1:21               ` Marc Rochkind
2016-07-01  1:34               ` John Cowan
2016-07-04 19:23                 ` Dave Horsfall
2016-07-04 19:56                   ` Ronald Natalie
2016-07-01  2:35               ` Nemo
2016-07-01  3:01                 ` Kurt H Maier
2016-07-01  3:52               ` Lyndon Nerenberg
2016-07-01 12:47                 ` [TUHS] MS-DOS William Cheswick
2016-07-01 13:43                   ` Marc Rochkind
2016-07-01 21:58                     ` John Cowan
2016-07-01 22:27                       ` Jacob Ritorto
2016-07-01 22:54                         ` Jacob Goense
2016-07-01 23:44                         ` John Cowan
2016-07-02  0:08                           ` Steve Nickolas
2016-07-02  1:09                           ` Kurt H Maier
2016-07-02  2:59                         ` Dave Horsfall
2016-07-02  3:27                         ` Greg 'groggy' Lehey
2016-07-02 23:21                           ` Dave Horsfall
2016-07-01 23:49                     ` Dave Horsfall
2016-07-02  1:12                       ` Steve Nickolas
2016-07-02  4:37                       ` SZIGETI Szabolcs
2016-07-02  9:53                         ` Brantley Coile
2016-07-01 13:47                   ` Clem Cole
2016-07-01 15:13                     ` Steve Nickolas
2016-07-02 15:25                       ` Ronald Natalie
2016-07-02 15:32                         ` Steve Nickolas
2016-07-02 19:46                           ` Nemo
2016-07-03  1:18                             ` Steve Nickolas
2016-07-03 13:33                               ` Nemo
2016-07-01 17:39                     ` John Cowan
2016-07-02 15:17                       ` Ronald Natalie
2016-07-03 22:07                   ` Derek Fawcus
2016-07-02 23:32         ` [TUHS] Algol68 vs. C at Bell Labs Peter Jeremy
2016-06-30 15:52     ` Joerg Schilling
2016-06-30 20:47     ` Lawrence Stewart
     [not found] <mailman.19.1467287486.30583.tuhs@minnie.tuhs.org>
2016-06-30 13:15 ` David
2016-06-30 13:18   ` William Cheswick
2016-06-30 13:39     ` Clem Cole
2016-06-30 13:44 Noel Chiappa
2016-06-30 14:28 ` William Cheswick
2016-06-30 19:23 ` John Cowan
2016-06-30 17:17 Nelson H. F. Beebe
2016-07-01  9:32 ` Brantley Coile

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=2c674075-db86-827b-fd97-30921757e9ae@aueb.gr \
    --to=dds@aueb.gr \
    /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).