9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Karljurgen Feuerherm" <kfeuerherm@wlu.ca>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] So, why Plan 9?
Date: Mon, 11 Oct 2010 11:01:54 -0400	[thread overview]
Message-ID: <4CB2EEA2.944B.00CC.0@wlu.ca> (raw)
In-Reply-To: <AANLkTinO4jAj+T6A31r+fhWHoF6Nq6G=JLQQZuOysjae@mail.gmail.com>

Well, I think it depends also on who one is and what one can afford to do at a point in time. And "afford" isn't necessarily only measured in dollars :)

I would much rather spend $200 on a slick Plan9 box, but I can't afford, given my current state of texpertise, to risk a government-funded project on a research O/S where support is more difficult. So an Apple it is, for the time being (for a lot less than $5000, btw...)

That's not to denigrate Plan9 by any means. I'm looking at it, like it, and hope to continue learning the ropes. But at the immediate moment, I don't really have a realistic choice, even given that the help I've got from people on this list has been fantastic. So for me, the short term solution is the Apple, and ideally, the long-term solution will be Plan9.

K

>>> On Mon, Oct 11, 2010 at  9:39 AM, in message
<AANLkTinO4jAj+T6A31r+fhWHoF6Nq6G=JLQQZuOysjae@mail.gmail.com>, Bruce Ellis
<bruce.ellis@gmail.com> wrote: 
> Very succinct, and better than I could do 'til the coffee kicks in.
> 
> You could have pointed out that the entire source tree is smaller than
> the gcc manual.
> 
> But as I say - do what you like. I know people who would rather spend
> $5k on an Apple PC than $200 on a slicker plan9 box. I have my FS
> (venti + fossil) on a USB wristband. Take that penguin heads.
> 
> Just the semi-delirious jots from early morning brucee.
> 
> On Mon, Oct 11, 2010 at 4:53 AM, Nick LaForge <nicklaforge@gmail.com> wrote:
>>> why anyone should care about Plan 9 anyway
>>
>> Because: getting things right the first time around is much more of a
>> practical matter than you may at first realize.
>>
>> Nick





  parent reply	other threads:[~2010-10-11 15:01 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 [this message]
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
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=4CB2EEA2.944B.00CC.0@wlu.ca \
    --to=kfeuerherm@wlu.ca \
    --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).