From: Eris Discordia <eris.discordia@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] nice quote
Date: Sun, 6 Sep 2009 00:48:15 +0100 [thread overview]
Message-ID: <7DD53D7E8CD0E762B9896B7C@[192.168.1.2]> (raw)
In-Reply-To: <CB23B512-146D-41EE-923C-D7318E29C295@storytotell.org>
> Using your theories, please explain why Lisp and Plan 9 both hover around
> the same level of popularity (i.e., not very, but not dead either).
I don't think I can say anything in that respect that cannot either be
easily refuted or greatly improved upon by someone already reading this
list and just too busy with their own stuff to post. Some of them
explicitly avoid feeding the troll (that I be, supposedly).
Anyway, here's what I think: Plan 9 and LISP are different, evolutionarily.
LISP seems to me like a downsized reptile that has survived and been forced
to exist in the shadow of mammals after the Mesozoic while Plan 9 looks
more like a lemur. A rather recently developed mammal driven into a small
area by its close kin from a common ancestor.
And one primary note: I have come to understand, in part thanks to this
very list, that popularity isn't really a good measure of merit for
computer stuff but you asked about popularity so I'll try to focus on that.
(Case in point, there's a lot I read about on this list that I don't think
I'd hear about in a lifetime, and this isn't a popular list.)
**********
LISP evolved in a parallel path to the line of languages that descended
from ALGOL. It represented/represents a programming paradigm--whose
significance is beyond me but visible to CS people--and it used to also
embody an application area. That application area, at the time, overlapped
with the ambitions of some of the best experts in computation. LISP gained
momentum, became an academic staple, was the pride and joy of world's best
CS/CE departments. The application area got hit but the programming
paradigm was strong as before.
The paradigm has scientific value--which is again beyond me but I trust CS
people on that--so it continues to be taught at world's best CS/CE
departments and to up-and-coming programmers and future computer
scientists. SICP is witness to that. In the academy, LISP will live on as
long as the paradigm it's attached to lives on and is deemed significant.
Those same people who are educated in some dialect of LISP, as well as
other languages, found businesses and apply their knowledge; occasionally,
by way of their training in LISP. For whatever reason they see merit in it
that many self-educated programmers or those trained at lesser institutions
don't. Obviously, there aren't that many top CS/CE departments and those
with founder status or strongly influences by founder institutions are
still fewer. Hence, LISP's living dead state: "popularity" among the elite.
Mind you, the natural divide between the two groups can sometimes be a
cause of resentment and get non-LISP people badmouthing it.
**********
Plan 9, on the other hand, was supposed to be a drop-in successor to
UNIX--a natural step forward. It was supposed to satisfy long-time UNIX
users by deceiving them with a similar-looking toolset while implementing a
large change of philosophy whose impact would only become clear after
(previous) UNIX users had already settled in. The factors that kept it from
actually replacing UNIX everywhere are many.
One factor was timing. It reached various tiers of "ignorant masses" when
not one but multiple possible continuations of UNIX, all of them FOSS, had
already gained foothold (GNU/Linux and *BSD).
The other factor was its overly complex arrangement compared to the mundane
purposes of lowly creatures more or less like me. I have tried arguing why
Plan 9 as it is is a hassle on desktop systems and have been met with
criticism that mostly targeted my lack of computer aptitude in general
rather than my argument. I stressed what I termed "conceptual complexity"
of Plan 9's model of how things should be and the lack of _any_ user
friendly, albeit sane, abstraction on top of that complexity.
A third, more important, factor is that it was advocated to people who
probably couldn't understand how Plan 9 would serve them better than things
they heard of more regularly, where was this new thing's edge that
justified the cost of its adoption. I for one am still at a loss on that
matter. As a hobbyist, I lurk, and occasionally--they say--troll, around
here but I'm not keeping my huge media collection on a Plan 9 installation
or using Acme for entering multi-lingual (up to three languages until a
while ago, four recently) text. Either task would be extremely cumbersome
to do on Plan 9 (and this really has little to do with the OS itself). In
short, I won't be doing Plan 9 because it's Plan 9. I, and most of the
lowly ones, need further justification that either hasn't been presented or
is way above my, or our, head.
The fourth factor I can think of is Plan 9's owners' attitude towards it. I
once dared go as far as saying it was actually "jettisoned." For reasons
that are beyond me Plan 9 isn't seeing much attention from Bell Labs or its
creators. It currently seems to lack the Benevolent Dictator for Life
figure many FOSS projects have. The overall air around it is one of
dereliction even if it is in fact being actively worked on behind the
scenes. Whether this is desired is again beyond me.
As a final note I think I should draw your attention to Linux's and *BSD's
path of ascendancy. All of these OSs seem to have consecutively attracted
distinct groups of users: serious programmers/contributors/researchers,
startups, the pleb (that's my kind), and corporate users--in that specific
order. Plan 9 seems to have stopped at stage 2 (startups), or maybe it's
just progressing and I am unaware of the progress. Regardless, attracting
the pleb seems to be the key to entering corporate user market and
widespread popularity, i.e. the stage where corporations, hoping to win the
pleb or higher pleb (industries and businesses), are willing to sponsor
(read: bribe) universities, students, and their own R&D departments in
teaching, learning, and furthering the new thing's cause.
**********
I must stress again these are all my impressions; hallucinations, if you
will.
--On Saturday, September 05, 2009 13:30 -0600 Daniel Lyons
<fusion@storytotell.org> wrote:
> Eris,
>
> Using your theories, please explain why Lisp and Plan 9 both hover around
> the same level of popularity (i.e., not very, but not dead either).
>
> —
> Daniel Lyons
>
>
next prev parent reply other threads:[~2009-09-05 23:48 UTC|newest]
Thread overview: 130+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 14:29 ron minnich
2009-09-02 14:51 ` Rodolfo (kix)
2009-09-03 9:52 ` Greg Comeau
2009-09-03 11:15 ` Skip Tavakkolian
2009-09-03 13:59 ` Greg Comeau
2009-09-03 15:01 ` David Leimbach
2009-09-02 15:19 ` Enrique Soriano
2009-09-02 16:38 ` erik quanstrom
2009-09-02 16:56 ` David Leimbach
2009-09-02 16:58 ` Robert Raschke
2009-09-02 17:03 ` David Leimbach
2009-09-02 17:36 ` erik quanstrom
2009-09-02 18:08 ` Richard Miller
2009-09-02 18:27 ` David Leimbach
2009-09-02 18:35 ` erik quanstrom
2009-09-02 18:46 ` David Leimbach
2009-09-03 15:02 ` Uriel
2009-09-03 15:02 ` David Leimbach
2009-09-02 19:10 ` Jonathan Cast
2009-09-02 20:02 ` David Leimbach
2009-09-02 20:23 ` Jonathan Cast
2009-09-02 20:45 ` David Leimbach
2009-09-02 17:31 ` Eric Van Hensbergen
2009-09-02 18:25 ` David Leimbach
2009-09-02 18:47 ` ron minnich
2009-09-02 19:11 ` Brian L. Stuart
2009-09-02 19:32 ` David Leimbach
2009-09-02 22:59 ` Roman V Shaposhnik
2009-09-03 9:53 ` Greg Comeau
2009-09-03 11:24 ` Skip Tavakkolian
2009-09-03 12:01 ` tlaronde
2009-09-03 12:06 ` Brantley Coile
2009-09-03 14:03 ` Greg Comeau
2009-09-03 15:13 ` Jason Catena
2009-09-04 9:04 ` Greg Comeau
2009-09-03 14:02 ` Greg Comeau
2009-09-03 14:57 ` Robert Raschke
2009-09-04 9:04 ` Greg Comeau
2009-09-03 17:40 ` Brian L. Stuart
2009-09-04 9:03 ` Greg Comeau
2009-09-04 17:47 ` Brian L. Stuart
2009-09-04 18:01 ` Jack Norton
2009-09-04 20:18 ` Eris Discordia
2009-09-04 21:36 ` Daniel Lyons
2009-09-04 22:50 ` andrey mirtchovski
2009-09-05 14:14 ` Eris Discordia
[not found] ` <7AAFE4127E1DB57785BB273A@192.168.1.2>
2009-09-05 14:36 ` Eris Discordia
2009-09-06 1:58 ` Jason Catena
2009-09-06 3:38 ` David Leimbach
2009-09-06 18:29 ` Tim Newsham
2009-09-06 18:44 ` David Leimbach
2009-09-06 17:08 ` Eris Discordia
[not found] ` <9C0E59DDCCDD197FBD4EC404@192.168.1.2>
2009-09-06 18:05 ` David Leimbach
2009-09-06 18:34 ` James Chapman
2009-09-06 18:26 ` Tim Newsham
2009-09-06 18:40 ` David Leimbach
2009-09-07 8:54 ` Paul Donnelly
2009-09-07 9:07 ` Greg Comeau
[not found] ` <BB8E3A2E5419E566D0361D29@192.168.1.2>
2009-09-04 21:52 ` Jason Catena
2009-09-05 11:02 ` Richard Miller
2009-09-05 11:22 ` Akshat Kumar
2009-09-05 12:11 ` tlaronde
2009-09-06 20:04 ` Rudolf Sykora
2009-09-06 20:45 ` erik quanstrom
2009-09-07 7:51 ` Vinu Rajashekhar
2009-09-05 13:38 ` Anthony Sorace
2009-09-07 9:07 ` Greg Comeau
2009-09-07 9:39 ` Akshat Kumar
2009-09-07 15:49 ` Greg Comeau
2009-09-07 15:58 ` erik quanstrom
2009-09-07 20:56 ` Lyndon Nerenberg - VE6BBM/VE7TFX
2009-09-07 21:21 ` Federico G. Benavento
2009-09-07 21:33 ` Lyndon Nerenberg - VE6BBM/VE7TFX
2009-09-09 8:30 ` Greg Comeau
2009-09-09 11:22 ` erik quanstrom
2009-09-09 15:48 ` Charles Forsyth
2009-09-09 16:00 ` Russ Cox
2009-09-09 16:37 ` Abhishek Kulkarni
2009-09-09 16:51 ` Jack Norton
2009-09-09 16:07 ` erik quanstrom
2009-09-09 16:07 ` Akshat Kumar
2009-09-09 16:08 ` Richard Miller
2009-09-09 16:13 ` Richard Miller
2009-09-10 21:45 ` erik quanstrom
2009-09-11 7:54 ` Richard Miller
2009-09-11 10:21 ` erik quanstrom
2009-09-09 16:11 ` David Leimbach
2009-09-09 16:29 ` Jason Catena
2009-09-09 17:17 ` Skip Tavakkolian
2009-09-09 18:36 ` Jason Catena
2009-09-09 17:29 ` Iruata Souza
2009-09-09 17:57 ` Tim Newsham
2009-09-10 11:59 ` Eris Discordia
[not found] ` <99A870099C1B1D6560F4CF1A@192.168.1.2>
2009-09-10 15:58 ` hiro
2009-09-10 21:24 ` Eris Discordia
2009-09-09 8:30 ` Greg Comeau
2009-09-09 8:29 ` Greg Comeau
2009-09-05 14:27 ` Eris Discordia
2009-09-05 14:33 ` Eris Discordia
[not found] ` <B6F7A6BD1919CC67B621FDE3@192.168.1.2>
2009-09-05 14:36 ` John Floren
2009-09-05 14:51 ` Eris Discordia
2009-09-05 19:30 ` Daniel Lyons
2009-09-05 23:48 ` Eris Discordia [this message]
2009-09-05 18:26 ` erik quanstrom
2009-09-06 0:05 ` Eris Discordia
2009-09-06 0:17 ` erik quanstrom
2009-09-06 0:37 ` Eris Discordia
2009-09-06 0:56 ` erik quanstrom
2009-09-06 16:51 ` Eris Discordia
2009-09-06 17:32 ` tlaronde
2009-09-06 4:23 ` J.R. Mauro
2009-09-06 17:24 ` Eris Discordia
[not found] ` <393394D0A7F3F4A227F94CDA@192.168.1.2>
2009-09-06 18:03 ` Rob Pike
2009-09-06 19:26 ` Eris Discordia
2009-09-07 15:47 ` J.R. Mauro
2009-09-07 8:54 ` Paul Donnelly
2009-09-07 9:04 ` Daniel Lyons
2009-09-07 9:05 ` Vinu Rajashekhar
2009-09-07 9:05 ` Greg Comeau
2009-09-07 9:49 ` Daniel Lyons
2009-09-07 11:34 ` erik quanstrom
2009-09-07 16:00 ` Greg Comeau
2009-09-07 19:23 ` Eris Discordia
2009-09-09 8:29 ` Greg Comeau
2009-09-09 8:35 ` Paul Donnelly
2009-09-03 19:38 ` tlaronde
2009-09-03 21:55 ` Daniel Lyons
2009-09-03 22:01 ` Tharaneedharan Vilwanathan
2009-09-07 8:54 ` Greg Comeau
2009-09-04 9:15 ` Greg Comeau
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='7DD53D7E8CD0E762B9896B7C@[192.168.1.2]' \
--to=eris.discordia@gmail.com \
--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).