| From: | Andy Hall |
| Date: | 18 Apr 2001 at 00:18:51 |
| Subject: | Re: Voyager Image Decoders |
Hello Matt
On 17-Apr-01, you wrote:
>>> Then you underestimate the work involved in using datatypes to decode
>>> images. Apart from the fact that V would lose all speed gained from the
>>> internal decoders, you'd lose progressive decoding, the cleaner
>>> dithering, increase memory consumption..
Voyger's dithering is crap, and so is it's memory consumption. I can't say
I've noticed it being faster at decoding, although the benchmarks suggest
it.
> The main reasons for the "proprietary" route are speed (of the decoders,
> and development) and control (of the code, of the bugs, of when things
> get fixed). I doubt any software developer trying to develop something
> as complex as a web browser wants 99.9% of his bugs to be reliant on
> someone ELSE fixing their software.
Sorry where did you get 99.9% of bugs from?
>> and for those who want to stick with AmigaOS - under which they
>> registered their version of Voyager? I , personally, cannot stand any of
>> the Vapors team hatred of WarpUP
>
> I doubt any software developer trying to develop something as complex as a
> web browser wants 99.9% of his bugs to be reliant on someone ELSE fixing
> their software.
Your repeating yourself. And you don't answer the question. David Gerber's
statement was nothing short of unproffessional. So Amiga Inc. didn't go
MorphOS and PowerUP, but hey, PUP was unamigalike anyway.
> (note that before StormC 4 it was not viable to compile WarpOS
> applications in gcc like you could PowerUP ones or now can compile MorphOS
> ones. Buying everyone on the Vapor team who needs to compile V [that's 5
> people I can count off the top of my head] a copy of StormC 4.0 is NOT an
> option)
I and several other people have disscussed with Fleecy about going for GCC
as a standard compiler, like morphOS, which he seem quite receptive too.
As Storm now is GCC too, there shouldn't be a problem from H&P. It'd be,
go for Geekgadgets if you want a free option with no hand holding, go for
Storm if you want a complete IDE. Simple.
Personally I've yet to find a compiler that suits me, storm was crap, the
demo didn't work properly, DICE won't compile anything properly, VBCC
crashes my system, and GCC is far too complicated to get going. I hate to
admit it, but it is far easier to use a PC!
>> ...an i also cannot forsee many people bein so pro-MorphOS when the time
>> comes around for paying for it.
>
> Isn't that *your* tough tits, that you'll not have a decent browser to use
> on your brand spanky little AmigaOne box? :)
Well no, it is Vapor's if the community swings in favour of AOS4.0. Whilst
that is an if, surely it would make sense to cover all bases? Besides i
wouldn't call Voyager a decent browser YET. Theres still some way to go
before it is ready. 3.3 vould still become as crap as 3.2, the layout
engine may be much, much faster, but it still cacks things up more often
than either of the other browsers. Don't count your programs before they
reach the release version.
Regards
=========Powered By Amiga=========
== A1200T/040@28 18Mb 4.3Gb HDD ==
==================================
http://www.jgen.fsnet.co.uk
------------------------ Yahoo! Groups Sponsor ---------------------~-~>
Secure your servers with 128-bit SSL encryption!
Grab your copy of VeriSign's FREE Guide,
"Securing Your Web site for Business." Get it now!
http://us.click.yahoo.com/KVNB7A/e.WCAA/bT0EAA/d8AVlB/TM
---------------------------------------------------------------------_->
Quote carefully and read all ADMIN:README mails
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/