🚀 go-pugleaf

In article <311A2D98.4D87@harbornet.com> GIJoe <th_assoc@harbornet.com> writes:

>I dnTim Shea wrote:
>> Too many client are using 16 bit windows.  I'm not going to move to
>> 2.0 until there is a lot more 95 out there in government & corporate
>> situations, or a client requests it for some reason.

>Yet at home, these same managers are getting used to Win95 on their
>machines.  IDC quotes a 30% market share 12/95 for the first 
>three months Win95 was out...and projects a share of 60+% by end 1996.  
>That doesn't even include NT.  Even shareware is moving
>into 32bit(look at jumbo and shareware.com).  I believe MS's aggressive 
>NT selling campaign is going to allow a lot of purchase orders to
>be raised this summer for 32bit VB apps.


Very soon after Win95 came out, there was a lot of Internet traffic generated 
as people ran into problem after problem, and I think that the majority of 
people are quite reasonably "waiting."  This is Win95 "Release 1.0" and we all 
know what that means.

Nor are we particularly in a hurry.  The nice thing about Delphi is that both 
a 16-bit and a 32-bit product are in the same box at the same price, so that 
as developers and users gradually move to 32-bit environments, having stuck 
their own toothpicks into the pie and observed that now it's coming out clean,
Delphi remains a good tool to use.

Will Delphi "go supernova" or whatever-you-said?  Sure.  It already has.  
Great tools that help people make money and solve problems have a way of doing 
that -- and each one of us who may be "advocates" in a particular newsgroup 
can acknowledge that our own "personal favorite" product has had its own day 
in the sun.  This is simply Delphi's moment.

/mr/