9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Ed edbrown@binc.net
Subject: [9fans] Plan 9 future
Date: Fri, 12 May 2000 19:58:06 -0500	[thread overview]
Message-ID: <20000513005806.Iav2sFrf9y86rVap_TUFP4EPM3O4__Bl58_Wnrxuh50@z> (raw)

"G. David Butler" wrote:

>
> In any case, given that an Open Source model is not an option, how
> do we proceed?
>

Proceed practically....

If I can throw in my 5 cents...

I have a practical use for Plan 9.  I would like to develop a public safety software
system that  would cater to both small and large public safety organizations.   I will be
funding the project myself .  Since the project will take a year or more I must choose the

platform wisely.

What I don't care about:
    Open Source:  It's neat but not a deciding factor
    Free:  It's neat but not a deciding factor .

What I care about.
    The cost to me for developing an application  (my time spent programming, cost of
tools...)
    The cost to my customers  (operating system costs, misc. software costs)

I have no interest in tweaking the kernel or compiler suites, or mangling the clean
interfaces.  If Lucent sets a fair pricing structure that I believe will not stifle my
business then I will choose to develop my application on Plan 9.  It is my belief that
others like me would also choose Plan 9.

BTW, I like the direction that GDB has taken this discussion.  Let's hope this next
release of Plan 9 takes a better turn (read more profitable) than the last CD release.


Cheers,

Ed Brown
Minimano Labs, Inc.
edbrown@binc.net










             reply	other threads:[~2000-05-13  0:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-13  0:58 Ed [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-05-12  9:20 Will
2000-05-12  3:56 G.David
2000-05-11  5:26 Lucio
2000-05-11  4:57 Lucio
2000-05-10 23:19 G.David

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=20000513005806.Iav2sFrf9y86rVap_TUFP4EPM3O4__Bl58_Wnrxuh50@z \
    --to=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).