Hello Jools
On 03-Jan-02, you wrote: > oh. i timed voyager on that page. 11 minutes :) thats just under 100 times > slower than iprobe :) IProbe barely supports a tenth of what V does. You can't compare a slim old test version to an almost fully functional browser. If AWeb takes less time then good for AWeb. Same for IBrowse. I'm really pleased for them. Now I will explain that bug again for the benefit of people who don't pay any attention. Sites with a lot of text will be slow. There is a bug that means for every object (link, gadget, table cell) it will probably get slower and slower the more actual page content appears, until you get to about a megabyte or so of raw text, at which point V will look as if it's dead and suck up all your CPU time. If V is slow, then tough shit for now. There is a bug. Please do not report speed issues anymore. There is a bug. We know there is a bug. It affects speed. Got it? I'd be more interested in your "no tabs in plaintext" kinds of bugs, and your "whoops, V decoded this image badly" kinds of bugs. "It's slower than another browser" isn't interesting. -- Matt _____________________________________________________________________ Voyager Mailing List - http://v3.vapor.com/ Voyager FAQ....: http://faq.vapor.com/voyager/ Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE
