From: Larry McVoy <lm@bitmover.com>
To: Miles Lane <miles@megapathdsl.net>, linux-kernel@vger.kernel.org
Subject: Re: ANNOUNCE New Open Source X server
Date: Wed, 18 Apr 2001 19:20:30 -0700 [thread overview]
Message-ID: <20010418192030.F29903@work.bitmover.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10104181317440.1478-100000@www.transvirtual.com> <15070.4428.345455.994818@pizda.ninka.net> <20010418192824.A21365@rochester.rr.com> <3ADE2EBD.8A875AE1@megapathdsl.net> <20010418215602.A9035@rochester.rr.com>
In-Reply-To: <20010418215602.A9035@rochester.rr.com>
On Wed, Apr 18, 2001 at 09:56:03PM -0400, Scott Prader wrote:
> [much stuff about X]
Scott, I think in part what people are reacting to is the "Hi, I'm going
to start a new project, it will be cool, you should come work on it".
Forgive me if I got it wrong, I'm paraphrasing, but wasn't it something
like that what you said?
Here's my two cents on why you got the reaction you got. Reality is
settling in. I think people ar becoming aware that there aren't really
18,000 projects with 145,000 developers all hacking away on SourceForge.
Think about it - Red Hat comes with about 900 rpms. So what's in
the other 17,100 projects? The point being that while those projects
numbers sound impressive, I think we all know that 95% of them aren't
going anywhere.
In other words, what the world does not need is another project. What
the world does need is people who roll up their sleeves and do real work.
You may well be one of them, that would be cool. But what would be even
cooler is if we join together on real, existing efforts and work on them
rather than just constantly make up a new project. Yeah, it's a lot harder,
you have to put at least part of your ego aside and accept someone else's
leadership, but more gets done that way.
If you are still reading, my advice is to have a beer, relax, and ask
yourself which is more cool - a new project with about 1/100 chance
of going somewhere or contributing much more than 1/100 to an existing
project with proven track record.
Besides, there are some sharp cookies over there in X land, you are more
likely to have fun working with them.
> "You can tune a filesystem, but you can't tuna fish." -unknown
I am 99.9% sure that Kirk McKusick put that in the BSD man page.
If it wasn't him I'll bet it was Bostic or Joy, but my bet is on Kirk,
he wrote UFS. Someone at Sun took it out, and I put it back in in SunOS
4.1.1 in the tunefs.8 man page with the following comment above it (yeah,
I really did spell daemon the wrong way, shame on me):
.\" Take this out and a Unix Demon will dog your steps from now until
.\" the time_t's wrap around.
.sp
You can tune a file system, but you can't tune a fish.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2001-04-19 2:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-18 22:02 ANNOUNCE New Open Source X server James Simmons
2001-04-18 22:12 ` David S. Miller
2001-04-18 23:28 ` Scott Prader
2001-04-19 0:18 ` Miles Lane
2001-04-19 1:56 ` Scott Prader
2001-04-19 2:20 ` Larry McVoy [this message]
2001-04-19 3:53 ` Richard Gooch
2001-04-19 3:54 ` Alan Cox
2001-04-19 4:05 ` Scott Prader
2001-04-19 12:06 ` [WAAAY OT]Re: " Mark Salisbury
2001-04-18 23:57 ` Miles Lane
2001-04-19 8:05 ` [Linux-fbdev-devel] " Sven LUTHER
-- strict thread matches above, loose matches on Subject: below --
2001-04-19 17:16 James Simmons
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=20010418192030.F29903@work.bitmover.com \
--to=lm@bitmover.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@megapathdsl.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