Xref: utzoo comp.sys.ibm.pc:51995 comp.windows.ms:2565
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!ux1.cso.uiuc.edu!aries!mcdonald
From: mcdonald@aries.scs.uiuc.edu (Doug McDonald)
Newsgroups: comp.sys.ibm.pc,comp.windows.ms
Subject: Re: Windows-the interface that may never happen...
Message-ID: <1990Jun6.153908.14746@ux1.cso.uiuc.edu>
Date: 6 Jun 90 15:39:08 GMT
References: <4ad6ea11.20b6d@apollo.HP.COM>
Sender: usenet@ux1.cso.uiuc.edu (News)
Reply-To: mcdonald@aries.scs.uiuc.edu (Doug McDonald)
Distribution: usa
Organization: School of Chemical Sciences, Univ. of Illinois at Urbana-Champaign
Lines: 48

In article <4ad6ea11.20b6d@apollo.HP.COM> nelson_p@apollo.HP.COM (Peter Nelson) writes:
>
>
>
>
>
>From: doerschu@rex.cs.tulane.edu (David Doerschuk)
>
>>>          Until MicroSoft offers libraries for the masses, nothing will
>>>change.  Currently, if I want to develop software, I have to spend
>>>hundreds.  I bought Quick C  1.01 for $52 new, the upgrade for $45, why
>>>not libraries for windows at $80?
>>
>>I couldn't agree more.  MS wants an absurd amount of money for the
>>libraries. 
>
>  Is this the reason why products written for Windows seem to 
>  be so expensive?  
>
No.

It could be that the sellers just think "Oh Oh Windows adds so much value
to my product I'll charge more".

Or it could be that Windows programs are more expensive to develop.
I have written some. They are indeed more expensive.

First you have to learn how Windows works. Its not straightforward.
Even for people who have programmed the Mac. I takes months. 

Second, you have to program for Windows in **UNHOSTED** C. That is,
the Windows envrionment is and unhosted C environment. A large fraction 
of standard C language libray functions DON'T WORK: scanf, printf,
any form of stdio, puts, putc, malloc, free, the list goes on and on.

And the ways you have to do the equivalent in Windows are messy. You 
(if you follow the rules) HAVE to use mixed model programming
(unless you program is small enough to be medium model). The pointers
you get from Windows equivalent of malloc may BECOME INVALID without
your doing anything. It's more complicated than a simple change of
char * to char **. 

Windows graphics calls are fairly simple. But it takes a bit of work
to get them all just exactly in the right order.

And so on. 

Doug McDonald