[shell-coding] Re: VB

>I know both VB and C++ very, very well and use them everyday. VB is good
for
>quick playing around with ActiveX controls when performance doesn't matter.
>You'll be much happier for every thing else if you learn C++.

Ya, truthfully I started learning VB cuz MFC looked like voodoo magic at
first. I had no idea what window messages were, or function pointers, or
pretty much anything usefull. I was smack in the middle of a computer
science program that was content to do file io in cobol and ignore anything
that would land me a sucessfull position programming anywhere on the globe.
So, I picked up vb, learned the api's via msdn and countless books, got
certified, and then realized that mfc was exposing the usefull stuff the VB
is trying so hard to hide. The more I played with vb, the more I loved and
hated it. VB is great and quick for 90% of the apps most businesses or
enterprise programmers need, hell for that matter can handle. But man, if
you try and get outside of what vb controls, life quickly becomes a
nitemare, anything requiring threading, or function pointers, subclassing,
or just plaing API translation is a freakin nitemare sometimes. I think I
pretty much quit using the API viewer altogether cuz there was always some
constant or function not defined, so out comes textpad and into winuser.h or
some other header i go! lol, it's almost more effort to stay in vb, that it
was to just learn the wizardry that is mfc and pure C based windowed
methodology. And hence I am at the point I stand now, ActiveX ruled until I
started getting into dll hell from VB's "I'll change your component guid
when i see fit, unless you know how to manage a component" attitude, to
realizing that true COM components had much much more to offer that what VB
was letting shine thru. I almost want to go straight MFC, no COM to avoid
the mess, but I work with a couple of guys that are die hard vb, simply
because they are not die hard programmers, subclassing and the likes is a
completely foreign concept, as far as they know "forms" only have
load/unload events... lol, and refuse to be exposed to anything else. the
world is flat and that is that! Besides being forced to keep the code in a
readable format for the others by not jumping into ATL, VB would be out the
door in my world in 2 Seconds flat.

whew... sorry, just a rant, got a little bit frustrated as I recalled a few
fond VB memories. anyone else feel me on this?
-mark


__________________________________________________
Subscription options and archive:
http://www.freelists.org/list/shell-coding

Other related posts: