Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!columbia!read.columbia.edu!kearns
From: kearns@read.columbia.edu (Steve Kearns)
Newsgroups: comp.sys.mac.programmer
Subject: Re: ThinkSpeed C++--------
Message-ID: <6495@columbia.edu>
Date: 13 Sep 89 18:19:07 GMT
References: <336@castle.ed.ac.uk> <13519@well.UUCP> <6494@columbia.edu> <1478@bnlux0.bnl.gov>
Sender: news@columbia.edu
Reply-To: kearns@read.UUCP ()
Organization: Columbia University Department of Computer Science
Lines: 22

In article <1478@bnlux0.bnl.gov> drs@bnlux0.UUCP (David R. Stampf) writes:
>
>I have seen virtually *no* transfer of programs between the non-mac and 
>the mac world, so a "detour" is not such a problem.  The mac is a detour 
>in the inevitable march of mediocre computers. 
.......
>	Get real.  The LSC extensions are a powerful tool for using the
>mac.  Since mac code is inherently non-portable anyway, I don't see that
>it matters.
>
>	< dave

Read the trade journals and you will be aware of many programs which are
cohabiting both IBM and MAC.  Wingz will soon be on both, Microsoft Word
shares much, Microsoft Excel, Lotus 123 for the mac is coming, many
dbase clones, etc...  Several years ago I wrote a sophisticated DRAW program
which ported rather easily to Windows.  

In other words, more and more programs exist on both machines, in order to
serve organizations which have both machines.  

-steve