Path: utzoo!attcan!uunet!ginosko!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!purdue!iuvax!mailrus!sharkey!itivax!abaa!esker
From: esker@abaa.uucp (Lawrence Esker)
Newsgroups: comp.sys.amiga
Subject: Amiga's Strongpoints (long) (Was: Re: Denise/Paula/Agnus/Gary/Portia)
Summary: I stand corrected, sort of...
Keywords: Legal and System Supported
Message-ID: <927@neptune.UUCP>
Date: 10 Aug 89 15:56:52 GMT
References: <1388@bnr-fos.UUCP> <713@abaa.UUCP> <8566@batcomputer.tn.cornell.edu>
Reply-To: esker@abaa.UUCP (Lawrence W. Esker)
Organization: Allen Bradley, Ann Arbor
Lines: 82

In article <8566@batcomputer.tn.cornell.edu> riley@tcgould.tn.cornell.edu (Daniel S. Riley) writes:
 esker@abaa.UUCP (Lawrence Esker) writes:
<*In article <1388@bnr-fos.UUCP> protcoop@leibniz.uucp () writes:
<*>that the Amiga 3000 did not use Commodore's custom chips but used some
<*>'off the line' parts by other companies, for example the TI 34000 (?)
<*>blitter.  Let us further suppose that all of the system software looks
                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<*>the same to the programmer, i.e. all of the function calls are the same.
   ^^^^^^^^^^^^^^^^^^^^^^^^^^
<*>Would it not be possible for current software to work on both the new
<*>hardware and the old hardware?
<*                                            ...there are alot of developers
<*out there who, for whatever reasons, beleive they can get squeeze better
<*performance out of the machine by doing things their own way.  Look at how
<*much software breaks when there have been operating system changes...