The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] TUHS Digest, Vol 14, Issue 63
Date: Mon, 16 Jan 2017 14:46:27 -0500 (EST)	[thread overview]
Message-ID: <20170116194627.0FF8B18C085@mercury.lcs.mit.edu> (raw)

    > From: Larry McVoy

    > It is pretty stunning that the company that had the largest network in
    > the world (the phone system of course) didn't get packet switching at
    > all.

Actually, it's quite logical - and in fact, the lack of 'getting it' about
packets follows directly from the former (their large existing circuit switch
network).

This dates back to Baran (see his oral history:

  https://conservancy.umn.edu/handle/11299/107101

pg. 19 and on), but it was still detectable almost two decades later.

For a variety of all-too-human reasons (of the flavour of 'we're the
networking experts, what do you know'; 'we know all about circuit networks,
this packet stuff is too different'; 'we don't want to obsolete our giant
investment', etc, etc), along with genuine concerns about some real issues of
packet switching (e.g. the congestion stuff, and how well the system handled
load and overload), packet switching just was a bridge too far from what they
already had.

Think IBM and timesharing versus batch and mainframe versus small computers.

	Noel


             reply	other threads:[~2017-01-16 19:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-16 19:46 Noel Chiappa [this message]
2017-01-17  0:30 ` Brad Spencer
  -- strict thread matches above, loose matches on Subject: below --
2017-01-17 15:32 Noel Chiappa
2017-01-18 14:29 ` Paul Ruizendaal
     [not found] <mailman.1.1484532001.2693.tuhs@minnie.tuhs.org>
2017-01-16 16:00 ` Doug McIlroy
2017-01-16 16:22   ` Marc Rochkind
2017-01-16 16:44   ` Larry McVoy
2017-01-16 16:52     ` Marc Rochkind
2017-01-16 19:17     ` Steve Johnson
2017-01-16 19:21       ` Larry McVoy
2017-01-16 19:57         ` Ken Thompson
2017-01-16 23:41     ` Tim Bradshaw
2017-01-16 23:45       ` Brantley Coile
2017-01-17  4:07       ` Jason Stevens
2017-01-17  5:22         ` William Corcoran
2017-01-17 11:43     ` Jason Stevens
2017-01-17 14:27     ` Joerg Schilling
2017-01-17 14:21   ` 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=20170116194627.0FF8B18C085@mercury.lcs.mit.edu \
    --to=jnc@mercury.lcs.mit.edu \
    /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).