9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jack Norton <jack@0x6a.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] fun quote
Date: Thu, 17 Sep 2009 07:34:17 -0500	[thread overview]
Message-ID: <4AB22CC9.1090201@0x6a.com> (raw)
In-Reply-To: <bea77df70e15400d75c4603989655ad3@quanstro.net>

erik quanstrom wrote:
> i don't know how ingo managed to put his
> finger on so many reasons i enjoy plan 9
> by counterexample.
>
> Linux is a 18+ years old kernel, there's not that
> many easy projects left in it anymore :-/ Core kernel
> features that look basic and which are not in Linux
> yet often turn out to be not that simple.
> 	-- Ingo Molnar
>
> - erik
>
>
Now, Plan 9's kernel is pretty old too, isn't it?  If Plan9 had become a
bit more widely accepted, even as late as, let's say, 2002, do you think
it would have become an unruly and frighteningly complicated beast as
linux has?
What has saved other 'popular' kernels from this?  For instance, no body
ever complains about FreeBSD being a complex cluster f***, but it has
pretty wide adoption (even as a 'desktop').  What about OS X?  Has
Apple's arrogance and secrecy saved it from....  open source
development?  It seems like they release code only after they are damn
sure they've gotten all they can out of it.
So, is Linux the unwanted poster-child of open source development?  I
think an argument could be made.

-Jack



  reply	other threads:[~2009-09-17 12:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17 12:14 erik quanstrom
2009-09-17 12:34 ` Jack Norton [this message]
2009-09-17 12:52   ` erik quanstrom
2009-09-17 15:30     ` Jack Norton
2009-09-17 16:00       ` james toy
2009-09-17 16:05       ` David Leimbach
2009-09-17 16:02     ` David Leimbach
2009-09-17 16:27 ` matt
2009-09-17 16:45   ` erik quanstrom

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=4AB22CC9.1090201@0x6a.com \
    --to=jack@0x6a.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).