From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] more little hardware
Date: Thu, 18 Mar 2010 07:36:34 -0700 [thread overview]
Message-ID: <3e1162e61003180736l78ea1cbana41baebd7c99c4ff@mail.gmail.com> (raw)
In-Reply-To: <626501.10618.qm@web1204.biz.mail.gq1.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1669 bytes --]
On Thu, Mar 18, 2010 at 2:24 AM, Gabriel Díaz <gdiaz@rejaa.com> wrote:
> hello
>
> "How do I get my employer to need plan9?"
>
> Given the experiences posted by some of the plan9 inventors in other
> thread, this seems to be an almost impossible task, unless you make your own
> business or change you're employer for someone which already uses plan9. I
> guess.
>
> It is a bit discouraging for a fan who has the hope to get his employer
> need plan9 i think. I already gave up on this.
>
I think size of company matters too. We're a really small group where I
work, and getting things done correctly is actually valued a bit more than
the means by which it gets done.
It's that mentality that let me throw off the shackles of Java for Erlang
and Haskell for a lot of the code I'm responsible for. I might even try to
push my luck soon and get permission to rewrite a small but really important
chunk of code in Go if i can prove to myself, and then to others, that it's
a good idea :-)
Dave
>
> slds.
>
> gabi
>
>
>
> ----- Original Message ----
> From: Steve Simon <steve@quintile.net>
> To: 9fans@9fans.net
> Sent: Thu, March 18, 2010 9:04:56 AM
> Subject: Re: [9fans] more little hardware
>
> > Honestly, I think it would loads of fun to do, but I probably wouldn't
> use
> > it myself once done, I don't have the free time to do it, and I don't
> > know of a way to do it for work...
>
> The story of my (plan9) life...
>
> I should add that there is also lots of stuff I _would_ use
> that I don't have time to write.
>
> my big question is "How do I get my employer to need plan9?"
>
> -Steve
>
>
[-- Attachment #2: Type: text/html, Size: 2364 bytes --]
next prev parent reply other threads:[~2010-03-18 14:36 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 10:34 maht
2010-03-16 14:54 ` blstuart
2010-03-16 16:44 ` John Floren
2010-03-16 16:17 ` blstuart
2010-03-16 19:35 ` Tim Newsham
2010-03-16 19:46 ` John Floren
2010-03-17 4:03 ` Tim Newsham
2010-03-17 4:50 ` ron minnich
2010-03-17 14:38 ` David Leimbach
2010-03-18 6:59 ` Tim Newsham
2010-03-18 8:04 ` Steve Simon
2010-03-18 9:24 ` Gabriel Díaz
2010-03-18 14:36 ` David Leimbach [this message]
2010-03-18 15:42 ` Jorden Mauro
2010-03-24 22:28 ` Jack Johnson
2010-03-28 14:33 ` Georg Lehner
2010-03-18 12:46 ` erik quanstrom
2010-03-18 14:27 ` Patrick Kelly
2010-03-16 21:02 ` Patrick Kelly
2010-03-16 23:38 ` ron minnich
2010-03-16 23:47 ` Patrick Kelly
2010-03-17 9:05 ` Charles Forsyth
2010-03-17 14:02 ` Stuart Morrow
2010-03-17 9:35 ` hugh
2010-03-17 15:08 ` ron minnich
2010-03-17 2:05 ` David Arnold
2010-03-17 11:11 ` maht
2010-03-17 13:57 ` Stuart Morrow
2010-03-17 18:06 ` Jack Johnson
2010-03-17 19:13 ` John Floren
2010-03-17 19:49 ` Axel Belinfante
2010-03-17 19:57 ` Axel Belinfante
2010-03-17 20:11 ` John Floren
2010-03-18 6:53 ` Tim Newsham
2010-03-16 16:53 ` Jack Johnson
2010-03-16 17:10 ` Jack Johnson
2010-03-16 16:33 ` blstuart
2010-03-16 18:20 ` ron minnich
2010-03-16 19:24 ` blstuart
2010-03-16 17:12 ` Jack Johnson
2010-03-16 17:52 Jonas Amoson
2010-03-16 17:24 ` blstuart
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=3e1162e61003180736l78ea1cbana41baebd7c99c4ff@mail.gmail.com \
--to=leimy2k@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).