🚀 go-pugleaf

In article <4fef2l$4sck@news-s01.ny.us.ibm.net>,
stevez1@ibm.net (Steven R. Zuch) wrote:
>>The sizemaniac aka VB 4.0 doesn't fit into that strategy.
>
>My point was that MS can, and IMHO will, incorporate more
>OLE2 and OCXs into their next operating system, and therefore,
>the need to distribute so much run time stuff with VB 4 will
>not be required.  VB may even become bundled with the
>next OS, just like QBasic became bundled with DOS.

You're talking 3-10 years from now...
Win95 didn't come with any OCXs and the same is true for NT 3.51.
I doubt we'll see any in NT 4.0 either...

So, when you distribute your app two years from now, you'll most likely
include those OCXs anyway, because the oldtimers who run NT 3.51 (because
they never adapted to the Win95 UI) still haven't caught on...

Installing a typical VB app (or any app with alot of DLLs and stuff) could
soon become a nightmare. What does your installation program do when faced
with a network? VB4 Enterprise simply ignores it, and stated that it
had to be installed separatly on each workstation. So much for the ease
of distributing OCXs?

The only good solution I found (while being a network admin) was to
install everything in one directory on the server. Nothing in SYSTEM or
other places. Share the directory and away you go... This does indeed
affect the users perception of the application's size!

>My point was that if a third party has a nice software program,
>MS may be able to incorporate the best of such into the
>operating system.  Development languages may fall into
>this area.  MS has been incorporating disk defragmenters,
>backup software, compression, desktop file managers,
>fax software, etc ... into Windows, regardless how the
>developers felt.

No. They licensed disk defragmenter from Symantec and the backup software
from Central Point (or Arcada?). These are stripped down versions of the
full package, so the customer is encouraged to buy the whole package...

In any case, not one of the applications you mentioned was made with VB,
nor did they use any OCXs.


-- 
=\
 *=- R.Moberg, CD-Player Pro info @ http://www.sn.no/~mobergru/
=/