> But back to Olli. In my opinion Olli shouldn't spend his time optimizing
> memory managements routines to make Voyager run on less suited equipment.
> If a problem can be solved if the users upgrade their equipment to reflect
> what currently is appropriate, then this is the way the problem should be
> solved. He should rather spend his time making the JavaScript engine work
> properly etc. etc. etc.
Well, in my opinion, Olli knows better than us where V needs to be enforced.
Many of the problem of 'small config' can be related to memory, but many
other things ca happen..
If memory management is THAT bad (that I've no clue) I think improving it should
improve V's usability on every system. If it's planar routines that need to be
improved, well you may be right... But I'm sure that like in every program,
there are lots of
// To be improved
// Bad hack... should do the trick
// might run ... or not
// untested
in V's code... And what I'm pretty sure is if we can report problems and suggest
functionalities we'd like to see (I'd love the Tabs like in IB2, I'd love a
power arex port, I'd love 'arexx fast links', I'd love a customizable navbar,
I'd love voyager to manage http resume, to defer its download to a download
manager, to be bugless on javascript (even buggy javascript) to have a vrml
plugin ... etc... )
nothing gives us the ability to schedule V's development...
Imagine yourself developping something like V and having tons of betatesters
reporting 'old' bugs (well bugs you have corrected or are currently correcting,
or in fact any bug they can find) and telling you NOW you must do that... that
one is urgent... stop doing that one... where would be the fun ?
Being managed when working for a customer or a company is one thing, but V is a
personal project of Olli and he's able to find what must be done... And maybe
the bug report this thread started over is an essential one who knows ?
I agree JS is the most important addition between V and V3 according to what
I miss in voyager Ng, but it's maybe not the most urgent thing to fix.
I 'd like V3 to be even more stable than VNG (that is here almost as stable as
say... dir). Yep I want all the nice new features to work, and many other ones,
and we are billions (well hmm... hundreds ? (hope more)) to want that... but
I want a rock solid browser that doesn't crash or makes my system crash, or make
my other applis crash... I want to be able of browsing while doing a long ftp
transfer with another program without having to reboot.... I don't want netscape
on my amiga (at least as long as it doesn't have resource tracking and memory
prot (according to vapor, today's amigang os was vms).
Stay assured that Olli and his gang probably spend part of nights and
weekend coding on V (amongst others) and they know what needs to be done better
than us.
> Well, that's my opinion. I know a lot disagree because they don't want
> to upgrade their computer.
I don't need to upgrade my computer, but I don't agree, partly because some
of the people who reg (or 'll reg) V may want to use it on their low-end system,
partly because I find it selfish to say 'don't waste your time working on
something I have no problem with', and partly because mem management is the
fundation of softwares (and the amount of mem I have doesn't impact )..
And in fact, whatever we/you/I can write here won't change anything to V's
development timetable will it ?
Regards
Phil
____________________________________________________________
Voyager Mailing List - Info & Archive: http://www.vapor.com/
For Listserver Help: <[EMAIL PROTECTED]>, "HELP"
To Unsubscribe: <[EMAIL PROTECTED]>, "UNSUBSCRIBE"
