The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Kevin Bowling <kevin.bowling@kev009.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] OSI stack (Was: Posters)
Date: Wed, 6 Feb 2019 16:40:24 -0700	[thread overview]
Message-ID: <CAK7dMtALSJ3ZnrGXu4TtK-FrTfy0b6G0cMd67+jpGQOG+GwMaA@mail.gmail.com> (raw)
In-Reply-To: <20190206231852.5B33018C07B@mercury.lcs.mit.edu>

Seems like a case of winners write the history books.  There were
corporate and public access networks long before TCP was set in stone
as a dominant protocol.  Most F500 were interchanging on SNA into the
1990s.  And access networks like Tymnet, etc to talk to others.

TCP, coupled with the rise of UNIX and the free wheel sharing of BSD
code, are what made the people to talk to.

On Wed, Feb 6, 2019 at 4:19 PM Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
>
>     > From: Kevin Bowling
>
>     > I think TCP was a success because of BSD/UNIX rather than its own
>     > merits.
>
> Nope. The principle reason for TCP/IP's success was that it got there first,
> and established a user community first. That advantage then fed back, to
> increase the lead.
>
> Communication protocols aren't like editors/OS's/yadda-yadda. E.g. I use
> Epsilon - but the fact that few others do isn't a problem/issue for me. On the
> other hand, if I designed, implemented and personally adopted the world's best
> communication protocol... so what? There'd be nobody to talk to.
>
> That's just _one_ of the ways that communication systems are fundamentally
> different from other information systems.
>
>         Noel

  reply	other threads:[~2019-02-06 23:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06 23:18 Noel Chiappa
2019-02-06 23:40 ` Kevin Bowling [this message]
2019-02-06 23:52   ` Larry McVoy
2019-02-07  0:04     ` Kevin Bowling
  -- strict thread matches above, loose matches on Subject: below --
2019-02-07 19:04 Noel Chiappa
2019-02-07  1:03 Noel Chiappa
2019-02-07  0:45 Noel Chiappa
2019-02-07  0:02 Noel Chiappa
2019-02-07  0:11 ` Kevin Bowling
2019-02-06 17:49 Noel Chiappa
2019-02-06 18:22 ` Paul Winalski
2019-02-06 20:47 ` Kevin Bowling
2019-02-07 18:07   ` Grant Taylor via TUHS
2019-02-07 18:22     ` Andy Kosela
2019-02-07 18:50     ` Larry McVoy
2019-02-04 20:29 Noel Chiappa
2019-02-04 21:13 ` Bakul Shah
2019-02-04 21:34   ` Clem Cole
2019-02-05 18:01 ` Grant Taylor via TUHS
2019-02-03 18:49 Norman Wilson
2019-02-03 15:02 Noel Chiappa
2019-02-03 16:51 ` Grant Taylor via TUHS
     [not found] ` <CANCZdfq5PM9jFEi9=geC+CTnveXs5CprN7b+ku+s+FYzw1yQBw@mail.gmail.com>
2019-02-06 17:16   ` Warner Losh
2019-02-06 17:23     ` Larry McVoy
2019-02-06 23:37     ` George Michaelson

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=CAK7dMtALSJ3ZnrGXu4TtK-FrTfy0b6G0cMd67+jpGQOG+GwMaA@mail.gmail.com \
    --to=kevin.bowling@kev009.com \
    --cc=jnc@mercury.lcs.mit.edu \
    --cc=tuhs@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).