Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!samsung!think!mintaka!oliveb!stratus!cloud9!lectroid!bigbootay!jmann
From: jmann@bigbootay (Jim Mann)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Desqview vs Windows?
Summary: Word for Windows?  When??
Keywords: Word, Windows
Message-ID: <466@lectroid.sw.stratus.com>
Date: 12 Dec 89 14:05:40 GMT
References: <1640035@hpspcoi.HP.COM> <12238@vaxc.cc.monash.edu.au>
Sender: usenet@lectroid.sw.stratus.com
Reply-To: jmann@bigbootay.sw.stratus.com (Jim Mann)
Organization: Stratus Computer, Software Engineering.
Lines: 15

Word does not yet run under Windows. In fact, I've always thought that the
biggest strike against windows was that Microsoft, while encouraging (?)
others to write for Windows, has not yet provided Windows support for
their most popular word processor.

The (?) after encouraging in the above paragraph is because I really don't
think Microsoft has done more than talk up writing for Windows. If I want
to write an application that uses the Mac interface, I just have to buy
a good cheap compiler (Think's Lightspeed C, for example). The toolbox
routines, which provide windowing support, menuing, etc. are all basic to
the Mac.  If I want to write for Windows, I not only have to buy the
compiler but have to shell out $350 or thereabouts for the Windows
development kit. This is fine for big companies that want to port their
work to Windows. It's not so good for someone who just wants to hack around
a bit, and learn a bit more about how to write for Windows.