lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lynx-dev anonymous usage of Lynx (was Arizona)


From: Bela Lubkin
Subject: Re: lynx-dev anonymous usage of Lynx (was Arizona)
Date: Sun, 11 Oct 1998 02:21:49 -0700

Philip Webb wrote:

> one of my points is that highly valuable Lynx developer time is
> to some extent being used by people out there
> to get away with cheaper lazier solutions.
> responses & examples so far have tended to confirm my suspicion.

"highly valuable Lynx developer time" is mostly being used arguing
pointlessly about endless meta-issues raised by your misunderstanding
both the purpose of existing Lynx code and the process by which problems
get fixed.

Tom's put a prospective fix into pre.9, which you should download and
test (without adding your local hack).  The same fix could have been
developed in about the same amount of time without all this extra
discussion.  All that was asked of you was to give better information
about the conditions leading to failure.  With a lot of coaching, that
was eventually accomplished and Tom modified the code to deal with the
oddity -- a doubly symlinked directory -- that Lynx wasn't expecting.

Questions about topics like "are we wasting developer time on anonymous
features" are off-topic.  For one thing, developer time on Lynx is
provided freely by the developers.  Who are you to question how they
choose to freely spend their own time?  What gives you the right to
*demand* that attention be focused exclusively on solving your problem,
which you were the only person to report (and which has a trivial
workaround, when you happen to run into it -- shell out or ^Z, delete
your .lynxrc, then try the save again) ?

Calm down.  If you have a problem, report it.  If a developer shows
interest in fixing it, such as asking for information, you should be
happy to have attracted that attention; give the information and see
what happens.  The problem will eventually get solved.  Yelling won't
make things any faster or smoother.

>Bela<

reply via email to

[Prev in Thread] Current Thread [Next in Thread]