From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Is IBM ThinkPad R60e notebook compatible with Plan9?
Date: Thu, 10 May 2007 23:08:58 -0700 [thread overview]
Message-ID: <cf059624f64f3a2ce45ab5fa59409609@oarsank.ca> (raw)
In-Reply-To: <5d375e920705102248k42a46917p410d84fd4448df01@mail.gmail.com>
>> and will proactively slow me down because I have answer
>> questions about 'why doesn't this compile? what the f*** are you
>> doing here? where is this function you call (that I haven't written
>> yet)?' etc. Even ignoring those questions takes time.
>
> Has this ever really been a problem or it is pure speculation?
This is based on many years of hands-on experience.
> First you ask not to be bothered by anyone, and now you want people to
> email you so you can "let each other know where we're stepping on each
> other.'" I'm sorry, but I just don't get it.
Continuing the IMAP analogy, for me to put up fragments if client-side
IMAP message caching code would not do any good to anyone who isn't
intimately familiar with that specific problem space. Typically the
would-be downloader sees "IMAP" and latches on with the hope they will
find a tool that will help them sort and filter their mail. But when
they double-click on imcache.c they get some strange pop-up dialog
from Windows instead of the IMAP email client they were expecting.
Avoiding that requires an access filter. A semantic filter that keeps
the programming-naive away is a wonderful idea -- spam filtering for
programmer wannabes :-) -- but it aint out there yet. This could be a
work-in-progress that you could keep on /n/sources/contrib.
Meanwhile, I want to keep my IMAP code within the group of people I
know actually *know* how IMAP works, so that I can actually develop
the code.
I don't have a problem with releasing code for people to look at, play
with, compile, sell, whatever. That's why my escaped goo has a BSD
license on it. But I'm not going to put out any work I create unless
and until I (I, *I*, *me*, not anyone else) decides it's ready to be
seen in public. And nobody (*NO*body) has the right to tell me
otherwise.
> Plan 9 is the only "open source" project where this kind of ridiculous
> practices exist. Why on earth Plan 9 has to be different and drive
> everyone around crazy is beyond me.
Maybe we aren't trying to solve penis envy?
--lyndon
next prev parent reply other threads:[~2007-05-11 6:08 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 8:34 Antonin
2007-05-10 12:14 ` Antonin
2007-05-10 12:25 ` Federico Benavento
2007-05-10 13:33 ` Antonin
2007-05-10 13:45 ` Markus Sonderegger
2007-05-10 12:36 ` erik quanstrom
2007-05-10 14:35 ` Gabriel Diaz
2007-05-10 15:18 ` Markus Sonderegger
2007-05-10 13:46 ` C H Forsyth
2007-05-10 13:55 ` erik quanstrom
2007-05-10 14:15 ` C H Forsyth
2007-05-10 15:59 ` Devon H. O'Dell
2007-05-10 19:26 ` Uriel
2007-05-11 3:57 ` Vester Thacker
2007-05-11 4:24 ` Lyndon Nerenberg
2007-05-11 4:50 ` Lorenzo Fernando Bivens de la Fuente
2007-05-11 10:30 ` Markus Sonderegger
2007-05-11 11:58 ` Steve Simon
2007-05-11 4:42 ` Uriel
2007-05-11 4:47 ` Lyndon Nerenberg
2007-05-11 5:13 ` Uriel
2007-05-11 5:32 ` Lyndon Nerenberg
2007-05-11 5:48 ` Uriel
2007-05-11 6:08 ` Lyndon Nerenberg [this message]
2007-05-11 6:28 ` Uriel
2007-05-11 17:35 ` lucio
2007-05-11 19:24 ` Uriel
2007-05-11 19:52 ` lucio
2007-05-11 20:05 ` lucio
2007-05-11 22:35 ` Lorenzo Fernando Bivens de la Fuente
2007-05-12 4:11 ` lucio
2007-05-12 4:13 ` lucio
2007-05-12 0:43 ` Tom Lieber
2007-05-12 4:34 ` lucio
2007-05-17 9:50 ` Dave Lukes
2007-05-17 10:23 ` erik quanstrom
2007-05-17 11:25 ` matt
2007-05-17 11:52 ` Dave Lukes
2007-05-17 11:59 ` erik quanstrom
2007-05-17 13:04 ` W B Hacker
2007-05-17 17:53 ` lucio
2007-05-11 11:37 ` Russ Cox
2007-05-11 14:57 ` Paul Lalonde
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=cf059624f64f3a2ce45ab5fa59409609@oarsank.ca \
--to=lyndon@orthanc.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).