[4875] in SIPB bug reports
Re: bugs? never...
daemon@ATHENA.MIT.EDU (yandros@MIT.EDU)
Thu Sep 22 02:05:55 1994
From: yandros@MIT.EDU
Date: Thu, 22 Sep 94 01:50:33 -0400
To: yoav@MIT.EDU
Cc: bug-sipb@MIT.EDU, yoav@MIT.EDU
In-Reply-To: <9409212328.AA13917@bill-the-cat.MIT.EDU> (yoav@MIT.EDU)
To respond in reverse order...
and if we
get too many problems because of NCSA going lame, put it back...
I put those files there for a ``good reason''; because the NCSA
service was timing out. Flipping back and forth between having that
entry there and not having it there seems silly. Only putting it in
because we notice that people have already lost seems stupid.
NCSA has not gone
down for a while, and the likelihood of them going down for a while is low.
NCSA hasn't gone down for a while because they haven't done anything
new in months. People now (usually) change the default homepage and
no one looks at the `what's new' page anymore, since it never gets
updated, so the load is gone. Once they release 2.5, the load will go
up again. (debates as to wehter or not NCSA will ever produce anything
useful or interesting again are welcome, offline. :-)
(remember, it tends to be several machines..
Yes, it's the same 4 machines now that it was then. It melts down
anyway.
Let me put this another way: Is there a *single* good reason to *NOT*
have a local copy? If you're worried that it might be out of date,
then just label the silly thing. If you think that it never gets
used, then you're very mistaken. If anything, I would argue that you
are pretty much *obligated* to provide a local help system, since the
one you're advocating using is not now and will never be in sync with
the version of the program that you've installed...
Maybe we should take one of Scott's old suggestions and settle this
via personal combat? ;->
chad
