🚀 go-pugleaf

In article <3257.885.uupcb@freddy.ersys.edmonton.ab.ca> stephen.murphy@freddy.ersys.edmonton.ab.ca (Stephen Murphy)  writes:
[...questions & answers deleted...]

>Diatribe: VB is suited for small in house applications
	[...some of of diatribe against VB deleted...]

>downloading an application, unzip it and find:
>VBRUN200.DLL, STATUSBR.DLL, SUPRCNTL.DLL, 3DGAUGE.DLL...
>Run the poor EXE and watch it turn your 486 into molasses
>as it tries to locate all the information it needs,
>sometimes coming up empty-handed, leaving a gaping
>hole in your video where that 3D Button is supposed to be.
>|
>Conclusion: If you've just finished a VB app that you feel
>you must share with the world, at least give it a tell-tale
>name. Don't call it "MYWIN.ZIP", call it "MYVB.ZIP". Better
>yet, say to yourself, "OK. This is what I want my
>application to look like. Now I'm going to learn C
>or C++ and write the *real* version!" You will both help
>and thank yourself tenfold in the long run.

	It's difficult to know which items you are complaining
	about here, but it appears that you don't like the fact
	that the app comes in several parts, including several
	DLLs.
	
	I have news for you - this is not limited to Visual
	Basic.  Many apps come with 1 or more DLLs, because
	that's the way it's done.  It is entirely independent
	of the programming language.  Before DLLs, the libraries
	were linked into the .EXE files - now they are external.
	If the DLLs were linked in with the .EXE, the .EXE would
	be quite large, but you wouldn't be complaining because you
	wouldn't know that several .EXEs contained exactly the
	same libraries.  On the other hand, your system would
	complain, because you would be wasting a significant
	amount of memory when any 2 or more of these apps containing
	a particular library were running simultaneously.

	I think the only thing you can complain about here is that
	VBRUN200.DLL is being packaged with each VB app made available.
	If the author assumes you have it and you don't, then the
	app doesn't work.  If he packages it with the app, then
	people complain about it wasting banwidth.  The same could
	be said for apps in any language that use common DLLs
	(i.e. Borland's custom controls).

	Don't blame VB or any other language.  If anything, blame
	the fact that all of these apps are pretty fancy and run
	in a GUI environment - that's why they are big.

	No, I don't use VB: I use BC++.

-- 
John A. Grant						jagrant@emr1.emr.ca
Airborne Geophysics
Geological Survey of Canada, Ottawa