Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uunet!decwrl!ucbvax!unisoft!bdt!david
From: david@bdt.UUCP (David Beckemeyer)
Newsgroups: comp.sys.atari.st
Subject: Re: TT (Who has one?)
Keywords: long
Message-ID: <3992@bdt.UUCP>
Date: 24 Jul 90 15:55:25 GMT
References: <1990Jul19.160526.2215@arcsun.arc.ab.ca> <6764@vax1.acs.udel.EDU> <1990Jul20.141733.5567@cunixf.cc.columbia.edu> <1990Jul20.233102.24577@math.lsa.umich.edu>
Reply-To: david@bdt.UUCP (David Beckemeyer)
Organization: Beckemeyer Development Tools, Oakland, CA
Lines: 27

I just wanted to comment on one thing Howard said:

In article <1990Jul20.233102.24577@math.lsa.umich.edu> 
  hyc@math.lsa.umich.edu (Howard Chu) writes:
>I am. If it's running Unix, (which seems to be the only sensible thing to
>do with an '030 at your disposal...  }-) software support is a non-issue.
>Usenet has always been better software support than any program I've ever
>seen from any vendor.

I disagree that software support for Unix is a non-issue.  Perhaps that
may be true for a "toy" machine (for personal use), but for professional
development, one really hairy driver bug which the vendor can't fix can
really foul up a project and cost lot's of $$$.

End-user training type support isn't a big deal.  There are lot's of people
that can help with that.  It's the vendor supplied drivers and kernel hacks
that can be a problem if the vendor can't (or won't) fix broken things,
especially if you're a VAR and want to sell the platform to clients.
The thing has to work.  The turn-key system buyer isn't going to spend
time on Usenet getting support.


-- 
David Beckemeyer (david@bdt.UUCP)	| "I'll forgive you Dad...  If you have
Beckemeyer Development Tools		| a breath mint."
P.O. Box 21575, Oakland, CA 94620	|    Bart - "The Simpsons"
UUCP: {uunet,ucbvax}!unisoft!bdt!david	|