The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ches@cheswick.com (William Cheswick)
Subject: [TUHS] MS-DOS
Date: Fri, 1 Jul 2016 08:47:01 -0400	[thread overview]
Message-ID: <7C35A731-84A0-4B9F-AEE6-8D9D1A06B315@cheswick.com> (raw)
In-Reply-To: <D64E62F3-EE85-462A-8617-657EAF6E3A6D@orthanc.ca>

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

>>​...​why didn't they have a more capable kernel than MS-DOS?
​>I don't think they cared. or felt it was needed at the time (I disagreed then and still do).

MS-DOS was a better choice at the time than Unix. It had to fit on floppies, and was very simple.

“Unix is a system administrations nightmare” — dmr

Actually, MS-DOS was a runtime system, not an operating system, despite the last two letters of its name.
This is a term of art lost to antiquity.
Run time systems offered a minimum of features: a loader, a file system, a crappy, built-in shell,
I/O for keyboards, tape, screens, crude memory management, etc. No multiuser, no network stacks, no separate processes (mostly). DEC had several (RT11, RSTS, RSX) and the line is perhaps a little fuzzy: they were getting operating-ish.

It all had to fit on a floppy (do I remember correctly that the original floppyies, SSSD, were 90KB?), run
flight simulator and some business apps.  MSDOS lasted a decade, and served the PC world well, for all its
crapiness.  Win 3.1 was an attempt at an OS, and Win 95 an actual one, with a network stack and everything.

>I agree with 90% of what he says, but not about Algol 68.  He obviously
>has a strong preference for small languages: it would be interesting
>to see his uncensored opinions of C++, the Godzilla of our day as Ada

I’d be astonished if he had anything good at all to say about C++.

He’s still around…you could ask him...


  reply	other threads:[~2016-07-01 12:47 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29 15:17 [TUHS] Algol68 vs. C at Bell Labs 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
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                 ` William Cheswick [this message]
2016-07-01 13:43                   ` [TUHS] MS-DOS 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
2016-07-02  0:12 [TUHS] MS-DOS Norman Wilson
2016-07-02  1:13 ` Steve Nickolas
2016-07-02  4:52   ` Random832
2016-07-03 19:40   ` scj

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=7C35A731-84A0-4B9F-AEE6-8D9D1A06B315@cheswick.com \
    --to=ches@cheswick.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).