> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of Julian Aronowitz > Sent: 20 November 2003 19:08 > To: [EMAIL PROTECTED] > Subject: [voyager] Re: What? > > > Hello Matt, > > On Thu, Nov 20, 2003, you wrote: > > ---- snip ---- > > Unfortunately for 68k users, until a 600MHz 68080 appears, > > some of the functionality of modern browsers is going to be > > far beyond your reach anyway, the same way that Aweb has > > split now into "APL" and "KHTML" versions to accomodate > > both, Voyager may do the same. > > > > MorphOS has some neat API's for some neat things, and the > > ability to run things at a blinding speed where on a 68k > > Amiga you would be left waiting for minutes. You just can't > > lead an old dog to suck eggs :) > > > > -- > > Matt Sealey <[EMAIL PROTECTED]> > > > > I do not know about anyone else but whenever I > speak with other Amiga users who normally have to > use systems other than the Amiga, irrespective of > what the Amiga can do, we all agree that we do not > expect the current Amigas (even those with 128 megs > of RAM and running 60 MHz with a Motorola '060) to > be able to do what a 600 MHz Amiga could do. That > is why we are waiting for the AmigaOne so we can buy > a replacement for our aging machines and continue to > enjoy Amigadom.
I agree. And when you get an OS to run on it, Vapor are still committed to evaluating the platform for a port, as Olli remarked years ago when the question first came up. > What we do expect from the developers of such > things as Voyager and AWeb is to correct some of the > inabilities or finish some of the upgrades to allow > those programs to continue to be able to access > sites. Sure. But you must understand that a great deal of the work progresses much faster on a 600MHz Amiga than it does on a 60MHz one. That's why all the neat stuff and bigfixes start on MorphOS and trickle back later. I'm simply warning you in advance though: Voyager may grow features that will never trickle back. > whether speed or RAM or some other aspect. For > example, there are more than one JAVA compilers for > the Amiga. Why is there no statement whether they > can work as an external plugin? Because compiling Java is not the same as running it. If you have a JVM, making it run as a plugin in Voyager is the work of a few minutes. > And, Javascript, why can IBrowse have a working 1.2 > version operatingand stable but not Voyager and AWeb? Voyager's Javascript implementation is up to scratch for 90% of the Core Javascript 1.3 specification. Certain Netscape extensions are unimplemented, and certain small amounts of the API are missing currently. Voyager's big discrepency is in it's DOM implementation, not the ability to execute Javascript. Certain operations are not implemented fully (function calls across framesets) but then again certain functionality *is* implemented to much greater degree of compatibility and completeness than IBrowse (event handlers, for example) Believe me, I know *precisely* what is wrong with Voyager, and also in Aweb and IBrowse too - it's in our best interests not to make the same mistakes as our competitors, and also to be abridged of anything like new features. And believe me when I say steps are being taken to fix all of the bugs currently known (and there are a few!) in V so you can all benefit. Please don't call us lazy or wish death upon us just because we prefer a PowerPC development box to a 68k one, and do work for money (both David and I work for Genesi doing lots of stuff OTHER than web browsers.. and Olli is busy coding software for a living too) rather than spending every waking hour on Voyager. -- Matt Sealey <[EMAIL PROTECTED]>
