9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Max E <maxxedout@comcast.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] So, why Plan 9?
Date: Tue, 12 Oct 2010 02:06:32 -0700	[thread overview]
Message-ID: <1286874392.3062.22.camel@maxtothemax-mint> (raw)
In-Reply-To: <d04fb692-689e-4380-8ea8-1c5588e80b43@c16g2000vbp.googlegroups.com>

For any use-case I personally care about (and probably any
workstation/server use case you care about as well,) the Linux kernel
with the GNU userspace will blow anything out of the water, both in
performance and usability. If you don't recognize this you're sticking
your head in the sand. I know P9 is faster in many ways, but have you
tried comparing performance figures with, say, browser rendering times,
Doom 3, or some video transcoder? Exactly.

However, projects like Linux and P9 can and *should* coexist, because
they complement each other. The developers of research OSs get a lot
more freedom to do research advance the state of the art. In fact, I'd
say P9 has contributed at least as much to the state of open-source OS
development as Linux has. Certainly, the Linux kernel uses a lot of
techniques that could only have been incubated within a research OS.
(/proc... what a wacky idea! But a good one.)

So, there are two reasons to use (and port your software to) Plan 9.
-First of all, you get a preview of what Unix development is probably
going to look like in a few years-- increased depreciation of ASCII for
Unicode, resource shared between computers, and so on.
-Second of all, Plan 9 is just SO DAMN FUN to play with.

-Max
On Mon, 2010-10-11 at 09:05 +0000, Mark Carter wrote:
> I was reading the suckless.org website the other day, and they seemed
> quite keen on Plan 9. I am running Linux. Is there a useful summary
> document that explains where plan9port fits in with Glendix, and why
> anyone should care about Plan 9 anyway (hope that doesn't come across
> as rude)?
>





  parent reply	other threads:[~2010-10-12  9:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-11  9:05 Mark Carter
2010-10-11 10:23 ` Sergey Zhilkin
2010-10-11 11:07 ` Robert Raschke
2010-10-11 11:17   ` Robert Raschke
2010-10-11 11:53     ` Nick LaForge
2010-10-11 13:39       ` Bruce Ellis
2010-10-11 14:45         ` ron minnich
2010-10-11 15:01         ` Karljurgen Feuerherm
2010-10-12  8:33       ` Aleksandar Kuktin
2010-10-12  8:51         ` Max E
2010-10-12 14:47           ` David Leimbach
2010-10-12 11:25         ` Steve Simon
2010-10-12 12:24         ` Jacob Todd
2010-10-12 16:04         ` Aleksandar Kuktin
2010-10-11 18:43     ` Brian L. Stuart
2010-10-12  8:17       ` Anssi Porttikivi
2010-10-12 14:09         ` Mark Carter
2010-10-12 14:53           ` Steve Simon
2010-10-12 14:59             ` David Leimbach
2010-10-12  9:06 ` Max E [this message]
2010-10-12  9:29   ` yy

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=1286874392.3062.22.camel@maxtothemax-mint \
    --to=maxxedout@comcast.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).