The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Marc Donner <marc.donner@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Research Datakit notes
Date: Tue, 28 Jun 2022 10:41:27 -0400	[thread overview]
Message-ID: <CAC20D2N4DFQDVPFUp78ztTQ-rWKbiAbkCZX7KSaTWsk-w=vxBQ@mail.gmail.com> (raw)
In-Reply-To: <CALQ0xCB-c8mBOVT+7Ud0sutuHx9OzUU1CXWhweFTBCZ2Kjb8BQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1209 bytes --]

On Tue, Jun 28, 2022 at 9:15 AM Marc Donner <marc.donner@gmail.com> wrote:

> My perception of the debate at the time was that it pitted proprietary
> networking (SNA, DECNet, ...) against open networking (TCP/IP).  The
> hardware vendors wanted proprietary networking to lock customers into their
> equipment, but that dog would not hunt.
>
Metcalfe's law: "*value of a network is proportional to the square of the
number of connected users of the system*." The problem with a walled garden
is that it can only grow as large as the walls allow.

>
> It was pretty clear that except for the clever encapsulation stuff that
> Vint had done with IP, the TCP/IP world was quick and dirty and quite
> slapdash.  But it was non-proprietary and that is what won the race.
>
Point taken, but I actually think it is more of a Christensen-style disruption
where the 'lessor technology' outstrips the more sophisticated one because
it finds/creates a new market that values that new technology for what it
is and cares less about the ways it may be 'lessor.'

I described this in a talk I did at Asilomar a few years back.  This is the
most important slide:
[image: ColesLaw20190222.png]

ᐧ

[-- Attachment #1.2: Type: text/html, Size: 3544 bytes --]

[-- Attachment #2: ColesLaw20190222.png --]
[-- Type: image/png, Size: 252558 bytes --]

  reply	other threads:[~2022-06-28 14:43 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-25 23:01 [TUHS] " Paul Ruizendaal
2022-06-25 23:09 ` [TUHS] " Larry McVoy
2022-06-25 23:57   ` Rob Pike
2022-06-26  1:17     ` Paul Ruizendaal
2022-07-02  2:51       ` Grant Taylor via TUHS
2022-07-02  2:57         ` Larry McVoy
2022-06-28 10:38     ` Derek Fawcus
2022-06-28 12:36       ` Rob Pike
2022-06-28 12:45         ` Rob Pike
2022-06-28 13:33           ` Dan Cross
2022-06-28 21:19             ` Lawrence Stewart
2022-06-28 21:34               ` Richard Salz
2022-06-29  6:07                 ` Stuart Remphrey
2022-06-28 16:11           ` Tom Teixeira
2022-06-28 18:28           ` John Floren
2022-06-28 12:47         ` Rich Morin
2022-06-28 13:13           ` Marc Donner
2022-06-28 14:41             ` Clem Cole [this message]
2022-06-28 15:54               ` Tom Teixeira
2022-06-28 17:05             ` Adam Thornton
2022-06-28 17:43               ` John Labovitz
2022-06-28 22:45               ` [TUHS] HTTP (was Re: Re: Research Datakit notes) Derek Fawcus
2022-06-26  1:41 ` [TUHS] Re: Research Datakit notes Anthony Martin
2022-06-26  9:52   ` Ralph Corderoy
2022-06-26 11:04   ` Paul Ruizendaal
2022-06-29 20:21   ` Paul Ruizendaal
2022-06-26  2:19 Noel Chiappa
2022-06-26  9:46 ` steve jenkin
2022-06-26 20:35   ` Erik Fair
2022-06-26 21:53     ` Steve Jenkin
2022-06-26 10:16 ` Paul Ruizendaal via TUHS
2022-06-26 13:07 ` John Cowan
2022-06-26 13:35   ` Larry McVoy
2022-06-26 13:58     ` John Cowan
2022-06-27  0:43 Noel Chiappa
2022-06-27  3:00 ` Erik Fair
2022-06-27 21:40 Noel Chiappa
2022-06-27 22:40 ` George Michaelson
2022-06-28 15:50 Noel Chiappa
2022-06-28 21:32 ` Lawrence Stewart

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='CAC20D2N4DFQDVPFUp78ztTQ-rWKbiAbkCZX7KSaTWsk-w=vxBQ@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=marc.donner@gmail.com \
    --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).