9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "J.R. Mauro" <jrm8005@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Question about Plan9 project
Date: Sat, 18 Jul 2009 14:49:06 -0400	[thread overview]
Message-ID: <3aaafc130907181149j126b1671x7cd948962a608266@mail.gmail.com> (raw)
In-Reply-To: <70328bb00907181135j6e7a1c1dvdc66e346b28409a3@mail.gmail.com>

On Sat, Jul 18, 2009 at 2:35 PM, dorin bumbu<bumbudorin@gmail.com> wrote:
> There are thousands of devices shipped with Microsoft Windows CE prior
> to version 4 (.NET). For these devices MS never offered patches even
> if these versions had lots of bugs, nor even standard C libraries
> (thank God there is wcecompat). And there are lot of projects that
> reached 10+ years (with workarounds, of course), and still in
> production. I don't think the risk of using Plan 9 is greather than
> the risk assumend by those who developed with WCE prior to 4.

I was going to say something to that effect -- Plan 9 is by and large
pretty stable, and on the same hardware, even no updates would leave
you with a fairly reliable system.

>
> Dorin
>
> On Sat, Jul 18, 2009 at 4:10 PM, Adriano Verardo<a.verardo@tecmav.com> wrote:
>> Hi all,
>>
>> As a professional user I think that Plan9 could be better than *nix for a
>> large class of  industrial - not time critical - applications but in Italy
>> nobody
>> use it, except of no more than a dozen of fans. The University doesn't know
>> it at all.
>> Of course, this is what I see. I would be happy if the picture were
>> different.
>>
>> Speaking with my clients I see that almost all appreciate Plan9. But, even
>> if some
>> of them defined it "fascinating", the common sense is that, without
>> guarantees about
>> its longevity, it could be a wrong choice.
>>
>> How can I reply to this objection ?
>>
>> Reading the thread about plan9.bell-lab.com I understand that Bell Labs
>> are no more directly committed in the project. Is it correct ?
>>
>> Adriano
>>
>>
>
>



  reply	other threads:[~2009-07-18 18:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-18 15:10 Adriano Verardo
2009-07-18 16:18 ` Skip Tavakkolian
2009-07-18 16:25 ` Anthony Sorace
2009-07-18 16:59   ` Uriel
2009-07-18 17:59     ` ron minnich
2009-07-18 19:29       ` Eric Van Hensbergen
2009-07-18 19:37         ` Corey
2009-07-18 19:50           ` Eric Van Hensbergen
2009-07-18 20:01             ` J.R. Mauro
2009-07-18 20:11             ` Corey
2009-07-18 23:21       ` Corey
2009-07-20 12:16       ` Iruata Souza
2009-07-18 20:40   ` Adriano Verardo
2009-07-19 12:38     ` Ethan Grammatikidis
2009-07-18 16:39 ` erik quanstrom
2009-07-18 18:35 ` dorin bumbu
2009-07-18 18:49   ` J.R. Mauro [this message]
2009-07-18 19:09   ` Adriano Verardo

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=3aaafc130907181149j126b1671x7cd948962a608266@mail.gmail.com \
    --to=jrm8005@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).