9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] the futility of #plan9 on irc
Date: Mon, 23 May 2005 17:57:01 -0600	[thread overview]
Message-ID: <c4432ecdd2bb83de695635c206c25c83@plan9.ucalgary.ca> (raw)
In-Reply-To: <20050523233359.GD14127@xware.cx>

> Sure, you might not like the IRC crowd, but posting this to 9fans in
> anger over a few members of #plan9 is about as mature

it's a good idea to forewarn other 9fans of the perils of
#plan9@freenode lest they make the mistake of joining.  of those 9fans
who have, in the past, visited the channel, 99% have left and haven't
looked back.  that's skip, geoff, charles, ron, russ, just off the top
of my head.  most of the new guys of the block have also at one time
or another quit with the promise to 'never come back'.

> #plan9 provides a multilingual, almost 24 hour/day, support service
> for free due to the efforts of its members.  

no, not really a 'support' service. more of a 'bash the newbie' service.

> It also serves a general port of call for those of us actively
> developing or porting to bounce ideas off of people in real-time -
> something that can't easily be done on (and isn't really suited
> for[2]) a public mailing list.

#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.

andrey/f2f



  reply	other threads:[~2005-05-23 23:57 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 [this message]
2005-05-24  0:03     ` Eric Van Hensbergen
2005-05-24  0:12       ` andrey mirtchovski
2005-05-24  4:29       ` Tim Newsham
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=c4432ecdd2bb83de695635c206c25c83@plan9.ucalgary.ca \
    --to=mirtchov@cpsc.ucalgary.ca \
    --cc=9fans@cse.psu.edu \
    /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).