Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!looking!brad
From: brad@looking.UUCP
Newsgroups: comp.society.futures
Subject: Re: (sun w/ iAEC-80n86 card)
Message-ID: <1079@looking.UUCP>
Date: Mon, 26-Oct-87 20:59:20 EST
Article-I.D.: looking.1079
Posted: Mon Oct 26 20:59:20 1987
Date-Received: Wed, 28-Oct-87 22:56:59 EST
References: <8710191851.AA11110@sdcsvax.UCSD.EDU>
Reply-To: brad@looking.UUCP (Brad Templeton)
Organization: Looking Glass Software Ltd.
Lines: 20

In article <8710191851.AA11110@sdcsvax.UCSD.EDU> hutch@sdcsvax.UUCP (Jim Hutchison) writes:
> [ On developing for IBM PCs ]
>Given that small point, there is also that developement notion.  Do *I* want
>to work on one of those pathetic/beastial/explitive devices?  Nay.  So I put
>up the bucks and buy a XXX with a YYY card/emulator in it.  Somewhere along
>the QC cycle it would be nice if you tested it on the target device, but you
>don't have to do developement on it.

In many cases, you couldn't be more wrong.  If you don't actually USE
the machine your writing for, you stand a high risk of not understanding
it properly and not writing for it properly.  This varies from application
to application, but it's a good rule of thumb.

When the AT came out, some developers, eager for the fastest machines,
developed and tested on ATs.  They got software that was too slow to run
on PCs.  Now you may say, "good, stamp out the 8088," but if your commercial
goal is to run on the PC you must do most of your testing on it.

-- 
Brad Templeton, Looking Glass Software Ltd. - Waterloo, Ontario 519/884-7473