Path: utzoo!attcan!uunet!samsung!dali.cs.montana.edu!milton!blake.acs.washington.edu!dlarson
From: dlarson@blake.acs.washington.edu (Dale Larson)
Newsgroups: comp.sys.amiga
Subject: Re: A3000's Shipping!
Message-ID: <4841@milton.u.washington.edu>
Date: 8 Jul 90 15:36:43 GMT
References: <719.2691DC21@weyr.FIDONET.ORG> <13058@cbmvax.commodore.com> <1990Jul5.193053.30153@cunixf.cc.columbia.edu>
Sender: news@milton.u.washington.edu
Organization: The Evergreen State College,  WA
Lines: 24

In article <1990Jul5.193053.30153@cunixf.cc.columbia.edu> es1@cunixb.cc.columbia.edu (Ethan Solomita) writes:
>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.
>>...  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.

WordPerfect has said that they're waiting for a release version of 2.0
to start fixing the fact that it can't even be run without crashing.
Since they said this in a letter dated a couple of weeks after I 
received the 2.0 release and since it took them 9 months to fix the
bugs it had running under 1.3 ffs, I'd say my office (which depends
on WP but also has projects requireing 2.0) is screwed!
--
	There are two ways to improve on human factors in computing:
 to make the programmers less stupid and/or to make the users less stupid.  
		Both are necessary, but neither is likely.
     -Dale Larson, Digital Teddy Bear (dlarson@blake.acs.washington.edu)