Stringsize 42 is not large enough to handle what a majority of the
search engines generate these days. The hotlist manager can't handle
strings for a growing number of URLS. Arachne is ten years behind the
time in memory management. Even Win3.x gave the option of "standard" or
"enhanced" mode, and DESQview proved 640 doesn't have to be a barrier.
We need a browser that will work on the web as it is designed today, and
with room for the changes coming tomorrow. Arachne isn't it, right now.
The question is, will Arachne ever be?
I don't want to go multi-OS on this system, but I'm being forced to it
because the browser I use now is becoming less and less functional. If
Arachne is going to stay around as anything other than an interesting
anachronism, the basic structure [in particular memory management] is
going to have to change. Until it does, I doubt https will ever be an
option for Arachne... encoding requires *reliable* accessible memory.
My 2cents worth.
l.d.
P.S. I doubt that any of us were confused by Glenn's bug fix. We knew
the likelihood of it showing up, even in version 1.70 wasn't too high.
P.P.S. Maybe if Arachne cleaned up after itself better, how many times
a string was used wouldn't be such a problem of "wasting?"
====
On Mon, 16 Oct 2000 01:08:44 +0200 (CEST), Michael Polak wrote:
> Maybe we can change STRINGSIZE to 42, but not to 80: it is used many
> times, and DOS memory is too limited for such wasting. Same with
> URLsize: we can increase it maybe to 300, but definitely not 1024.
-- This mail was written by user of Arachne, the Ultimate Internet Client
-- Arachne V1.66, NON-COMMERCIAL copy, http://arachne.cz/
