Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!psuvax1!rutgers!cunixf.cc.columbia.edu!cunixb.cc.columbia.edu!es1
From: es1@cunixb.cc.columbia.edu (Ethan Solomita)
Newsgroups: comp.sys.amiga
Subject: Re: A3000's Shipping!
Message-ID: <1990Jul5.193053.30153@cunixf.cc.columbia.edu>
Date: 5 Jul 90 19:30:53 GMT
References: <719.2691DC21@weyr.FIDONET.ORG> <13058@cbmvax.commodore.com>
Sender: news@cunixf.cc.columbia.edu (The Daily News)
Reply-To: es1@cunixb.cc.columbia.edu (Ethan Solomita)
Organization: Columbia University
Lines: 30

In article <13058@cbmvax.commodore.com> daveh@cbmvax (Dave Haynie) writes:
>As for 2.0 compatibility, the reason to keep 1.3 around is to give everyone
>a chance to fix their bugs.  Both Amiga programmers, who'll fix any 2.0 bugs
>they find, and applications programmers, who should fix their 1.3 bugs that
>break under 2.0.  Once 2.0 is ROMed, there will be no need to support 1.3
>anymore.  Good companies will have released bug fixes to their software where
>necessary, and not-so-good companies will be telling you the kind of support
>you'll get from them in the future.  

	Most of the companies I've spoken to (including NewTek and
Gold Disk) have stated that it is their policy to wait for 2.0 to be
finished before working on bug fixes because they say they don't know
if the bug is their fault or Workbench's fault. Gold Disk said that
all the problems with gadgets were problems with Intuition and that it
had nothing to do with them. If this attitude is prevalent we may have
to wait until after September before we get knew versions.


>-- 
>Dave Haynie Commodore-Amiga (Amiga 3000) "The Crew That Never Rests"
>   {uunet|pyramid|rutgers}!cbmvax!daveh      PLINK: hazy     BIX: hazy
>	"I have been given the freedom to do as I see fit" -REM


	-- Ethan

Ethan Solomita: es1@cunixb.cc.columbia.edu

"If Commodore had to market sushi they'd call it `raw cold fish'"
		-- The Bandito, inevitably stolen from someone else