9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Tim Newsham <newsham@lava.net>
To: Eric Van Hensbergen <ericvh@gmail.com>,
	Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] the futility of #plan9 on irc
Date: Mon, 23 May 2005 18:29:48 -1000	[thread overview]
Message-ID: <Pine.BSI.4.61.0505231823110.5020@malasada.lava.net> (raw)
In-Reply-To: <a4e6962a0505231703676d4cd4@mail.gmail.com>

>> #plan9 never has and never will serve as a developer channel.
>> signal/noise ratio is too low.  any useful comments are quickly
>> drowned in the sea of drivel.  grep the logs for expletives -- you'll
>> find more there than in a linux driver for sparc hardware.
>
> What's the solution then?  Having a more interactive venue to

Despite what Andrey said (most of which is true), IRC is still
the first place I'd recommend someone with a plan9 question
go ask.  Depending on who is watching, they could get a good
answer, or perhaps just a snide 'RTFM.'  When it works it
works well and when it doesn't, there's 9fans for a slightly
less timely response.

I also think IRC somewhat works for development chat.  People
who are interested in development can talk to each other.  Its
not hard to ignore people who arent contributing.

So, yah, you dont get free multilingual, almost 24 hour/day
support service for free... there's a cost -- occasional
newbie bashing, dick swinging and off-topic rants.  All told
still a good buy.

>      -eric

Tim Newsham
http://www.lava.net/~newsham/


  parent reply	other threads:[~2005-05-24  4:29 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-23 11:27 Russ Cox
2005-05-23 12:18 ` Vester Thacker
2005-05-23 17:44   ` Bruce Ellis
2005-05-23 17:46     ` Rob Pike
2005-05-23 18:43       ` Tim Newsham
2005-05-24  4:41     ` Dan Cross
2005-05-23 12:22 ` Uriel
2005-05-23 15:55   ` jmk
2005-05-24  0:54   ` Country Joe
2005-05-23 23:33 ` Chris Collins
2005-05-23 23:57   ` andrey mirtchovski
2005-05-24  0:03     ` Eric Van Hensbergen
2005-05-24  0:12       ` andrey mirtchovski
2005-05-24  4:29       ` Tim Newsham [this message]
2005-05-24 15:19         ` Russ Cox
2005-05-24 16:39           ` Vester Thacker
2005-05-24 16:43             ` William Josephson
2005-05-24 17:08               ` Vester Thacker
2005-05-26  4:02               ` McLone
2005-06-19 11:41             ` Vester Thacker
2005-06-19 11:43               ` Vester Thacker
2005-05-24 21:07           ` Chris Collins
2005-05-24 21:18             ` Russ Cox
2005-05-25 16:42               ` David Leimbach
2005-05-25 16:58                 ` Bruce Ellis
2005-05-26  9:17                 ` Abhey Shah
2005-05-24 21:20             ` Dan Cross
2005-05-24 21:31               ` Jack Johnson
2005-05-24 21:54                 ` Devon H. O'Dell
2005-05-26  4:04               ` McLone
2005-05-26  4:19                 ` Devon H. O'Dell
2005-05-26  4:29                 ` Dan Cross
2005-05-24  4:46       ` Dan Cross
2005-05-24  5:29         ` Lucio De Re
2005-05-24  0:14   ` Skip Tavakkolian

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=Pine.BSI.4.61.0505231823110.5020@malasada.lava.net \
    --to=newsham@lava.net \
    --cc=9fans@cse.psu.edu \
    --cc=ericvh@gmail.com \
    /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).