Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!sdd.hp.com!news.cs.indiana.edu!noose.ecn.purdue.edu!gn.ecn.purdue.edu!jess
From: jess@gn.ecn.purdue.edu (Jess M Holle)
Newsgroups: comp.sys.mac
Subject: Re: Mac Vs. Windows? (sorry)
Message-ID: <1991May19.163544.29111@gn.ecn.purdue.edu>
Date: 19 May 91 16:35:44 GMT
References: <1991May17.170732.13608@macc.wisc.edu> <9154566@bfmny0.BFM.COM>
Distribution: usa
Organization: Purdue University Engineering Computer Network
Lines: 41

In article <9154566@bfmny0.BFM.COM> tneff@bfmny0.BFM.COM (Tom Neff) writes:
>The *correct* approach is to start with what the customer actually wants
>to *DO* with their computer!  Whoa, scary concept there huh?  Jeez,
>what'll they think of next.  If you can characterize the APPLICATION or
>applications the customer has in mind, you can select SOFTWARE that does
>what he or she wants; and in turn sell them HARDWARE to support it.

If this approach is followed every time it will often lead to a PC if a
graphical user interface for all programs is not high on the list of 
priorities.

I have seen far too many friends and previous places of employment buy a
PC system simply because it offered a hardware and software combination
that could accomplish what they needed it to for the lowest initial cost.
This sounds good except for one small caveat, LOWEST-INITIAL COST.

Both a PC and Mac usually can offer a solution of some sort (niche 
applications not included) to any given problem. PC clones generally offer
lower initial costs. The unfortunate thing is that, though the PC does
accomplish the desired solution, it does not do so as easily (in MOST cases)
as a Mac. The aforementioned purchasers of PC systems that I have known
personally are then later disappointed at the lack of productivity that
their system yields in relation to a Mac. They are frustated by the lack
of universal integration between the Windows and PC mix of things that
they must live with, as compared to the nice integrated structure and
unified interface that is found on the Mac. This is generally not a problem
for the engineer who wants a machine to run a piece of equipment, take
measurements, and export values. This requires only a couple of applications,
plus perhaps a little hand-crafted code. The problem also does not effect
the person who only uses one program to accomplish their work. However, it
effects anyone who tries to integrate the results of a half dozen programs, as
well as those who have to integrate the results of others work with their own 
(especially when they are trying to integrate results of a totally different
type of program into their own). This can lead to a frustrating world of
translators and incompatibilities, as well as just plain operator inefficiency
caused by having to switch environments continuously.

In short (after all my ramblings), the above aspects MUST also be considered
when a new computer purchase is considered.

Jess Holle