Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!usc!samsung!uakari.primate.wisc.edu!uwm.edu!lll-winken!ncis.tis.llnl.gov!helios.ee.lbl.gov!nosc!crash!pnet01!wade
From: wade@pnet01.cts.com (Wade Bickel)
Newsgroups: comp.sys.amiga
Subject: Another 2-bit oppinion on what Commodor should do
Message-ID: <705@crash.cts.com>
Date: 14 Nov 89 09:16:22 GMT
Sender: root@crash.cts.com
Organization: People-Net [pnet01], El Cajon CA
Lines: 35

As long as everyone seems to be making all these suggestions as to what
Commodore should do, here is mine...
 
I think Commodore should look to the future now and start planning a machine
for the '90s.  It should take advantage of the Amiga's strengths and avoid
being trapped by its weaknesses.  On that note, I'd like to see a 68040
machine using a TI-34020 (or whatever is out then), with the TI graphics
processor replacing the special chips (actually, they should still be included
along with a compatibility mode).


 
My reasoning is as follows.  What makes the Amiga a great machine is the OS. 
It is the only multi-tasking enviorment which really fits on a PC.  Recently,
I've been forced to target code to an IBM platform, but I still do all my
coding on my Amiga.  Multi-tasking is addictive :^).  The Amigas graphics are
lagging, and the new "productivity" modes will do little to alieviate the
problem.  By switching to the TI graphics co-processors, a future upgrade path
will be assured.
 
Yes, I realize this would be painful to many of us, but in the end I'd rather
buy a new generation Amiga than have to switch to a 486 based machine running
half-OS (ie: OS/2 :^)).  Many programs would have to be rewritten, but with
the proper system level work by Commodore this could be made as painless as
possible.  Publishers would be able to sell a major upgrade, so they shouldn't
complain too much.
 
                                                Multi-Tasking in the wee
                                                   hours of the night,
 
                                                        Wade.

UUCP: {nosc ucsd hplabs!hp-sdd}!crash!pnet01!wade
ARPA: crash!pnet01!wade@nosc.mil
INET: wade@pnet01.cts.com