9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Kurt H Maier <khm@sciops.net>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Plan 9 in Brazil
Date: Sat, 29 Aug 2020 14:10:51 -0700	[thread overview]
Message-ID: <20200829211051.GA22116@wopr> (raw)
In-Reply-To: <e2a81ab2-c651-3fbb-aa07-91c6b3e5cf63@ReliableID.com>

On Sat, Aug 29, 2020 at 01:43:49PM -0400, Wes Kussmaul wrote:
> 
> On 8/29/20 1:25 PM, Leonardo wrote:
> > I really don't understand why Plan 9 has not been adopted. Legacy base?
> 
> By giving a lot of control to the user Plan 9 and its derivatives 
> undermine the Silicon Valley business model, which is built upon 
> breaking into your information home, taking your personal intellectual 
> property, and putting it on their balance sheets as a money making 
> asset. In other words, burglary and theft.

I'm with you on the topic of the ethical void rampant in a lot of SV
tech companies, but this take is off the mark.  SV businesses trade on
convenience; it's only late-stage multinationals that attempt to
leverage monopoly to remove user control.  Fortunately by that stage
they're poorly enough run that internal competition leads to senescense
and new challengers introduce choice again.  It happened to Nokia,
IBM, Microsoft, and it's currently happening to Google, but all of them
got to that late stage by selling stuff people wanted, not alone by
being jerks.

The new model is to burn venture capital to get that market control, 
but the same principal applies:  by the time you're big enough to exert
sufficient force to exploit a monopoly, you're sufficiently large that
internal competition prevents you from operating efficiently.  

I think AT&T's sense of entitlement regarding their IP, combined with
the fact that Plan 9 was never presented as a consumer-facing product
(it was a research platform) had more to do with any lack of uptake.  In
other words, had it proved popular, the vultures would have arrived and
done the same things they do on most platforms.  In this case, better
roosts had appeared by the time Plan 9 became something the vultures 
considered to be worth exploiting.

I am grateful to the people who put effort into letting us have the code
regardless of whatever we might imagine their motivations are.  I'm glad
we have access and that the access we have lets us shoot for whatever
targets align with our priorities.

khm

  parent reply	other threads:[~2020-08-29 21:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-02  8:52 Iruatã Souza
2020-05-02 16:31 ` [9fans] " Robert Sherwood
2020-08-29 17:25   ` Leonardo
2020-08-29 17:43     ` Wes Kussmaul
2020-08-29 18:36       ` Leonardo
2020-08-29 19:51         ` Wes Kussmaul
2020-08-29 21:10       ` Kurt H Maier [this message]
2020-08-29 19:54     ` Iruatã Souza
2020-08-29 21:03       ` Lucas Francesco
2020-08-29 22:09         ` Iruatã Souza
2020-08-31  2:52         ` Leonardo
2020-08-29 21:19       ` Lucas Francesco
2020-08-29 22:04         ` Iruatã Souza
2020-08-30 16:53       ` Leonardo
2020-08-30 19:40         ` Iruatã Souza
2020-08-31  1:29           ` Leonardo
2020-08-31  1:32             ` Kurt H Maier
2020-08-31  2:03               ` Leonardo
2020-08-29 21:30     ` ori
2020-09-01 11:52       ` Ethan Gardener
2020-09-01 12:10         ` hiro
2020-09-01 12:19           ` Ethan Gardener

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=20200829211051.GA22116@wopr \
    --to=khm@sciops.net \
    --cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).