From: Eugene Y Chang <eugene.chang@ieee.org>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Eugene Y Chang <eugene.chang@ieee.org>,
Frantisek Borsik <frantisek.borsik@gmail.com>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
Colin_Higbie <CHigbie1@higbie.name>,
libreqos <libreqos@lists.bufferbloat.net>
Subject: Re: [Starlink] musings on disruption and competition [was] It’s the Latency, FCC
Date: Wed, 1 May 2024 11:24:40 -1000 [thread overview]
Message-ID: <707A81F7-643E-4BCE-A1A9-AC2CA6689833@ieee.org> (raw)
In-Reply-To: <438D8F36-C1EF-4274-A7F7-95662BFE4D79@gmx.de>
[-- Attachment #1.1: Type: text/plain, Size: 1399 bytes --]
> On Apr 30, 2024, at 10:48 PM, Sebastian Moeller <moeller0@gmx.de> wrote:
>
> Hi Frank.
>
> On 1 May 2024 09:27:37 CEST, Frantisek Borsik via Starlink <starlink@lists.bufferbloat.net <mailto:starlink@lists.bufferbloat.net>> wrote:
>> Basically, Eugene, the situation you are describing is calling for a
>> competitor to disrupt them!
>
> [SM] Not a big fan of the silicon valley nomenclature... 'disruption' evokes thoughts of 'revolutionary' yet what typically happens is rather 'evolutionary' once one looks behind the marketing/hype... and that is not a bad thing, as real revolutions can be quite painful.
> That said, sure if the incumbents leave sufficient specialized demand unfulfilled that opens a niche/opportunity for competitors, but that IMHO is one of the core promises of market economies, and nothing that silicon valley created/realized de novo, no?
>
[EC] I also dislike the term “disruption”. It is just finding a hungry vendor that will fill the (our) need. I like a #3 that is trying to grow. Then if the larger vendor sees our goal is too insignificant to care, the smalller vendor will peel away (insignificant) market share and everyone is happy. If the smaller vendor starts taking away too much market share then the dominant vendor will change. This kind of change is better than talking to a dominant vendor sitting pretty.
Eugene Chang
[-- Attachment #1.2: Type: text/html, Size: 6666 bytes --]
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-05-01 21:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2779.1714503924.1074.starlink@lists.bufferbloat.net>
2024-04-30 19:31 ` [Starlink] " Colin_Higbie
2024-04-30 19:51 ` Eugene Y Chang
2024-04-30 21:07 ` Dave Taht
2024-04-30 21:22 ` Frantisek Borsik
2024-04-30 22:02 ` Dave Taht
2024-04-30 22:03 ` Dave Taht
2024-05-01 3:28 ` [Starlink] [LibreQoS] " Jim Forster
2024-05-01 7:23 ` Frantisek Borsik
2024-04-30 22:05 ` [Starlink] Fwd: " Rich Brown
2024-04-30 22:10 ` Dave Taht
2024-04-30 22:42 ` [Starlink] " Rich Brown
2024-04-30 23:06 ` Dave Taht
2024-04-30 22:31 ` Eugene Y Chang
2024-04-30 21:22 ` Eugene Y Chang
2024-04-30 21:35 ` Frantisek Borsik
2024-04-30 21:53 ` Eugene Y Chang
2024-05-01 0:54 ` David Lang
2024-05-01 7:27 ` Frantisek Borsik
2024-05-01 7:32 ` [Starlink] [LibreQoS] " Brian Munyao Longwe
2024-05-01 13:25 ` Jim Forster
2024-05-01 13:48 ` Brian Munyao Longwe
2024-05-01 13:57 ` Dave Taht
2024-05-01 8:48 ` [Starlink] musings on disruption and competition [was] " Sebastian Moeller
2024-05-01 21:24 ` Eugene Y Chang [this message]
2024-05-01 19:26 ` [Starlink] " Eugene Y Chang
2024-05-14 16:05 ` Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=707A81F7-643E-4BCE-A1A9-AC2CA6689833@ieee.org \
--to=eugene.chang@ieee.org \
--cc=CHigbie1@higbie.name \
--cc=frantisek.borsik@gmail.com \
--cc=libreqos@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
--cc=starlink@lists.bufferbloat.net \
/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