[Detector]

Ah, the VB.NET vs VB6 debate.

Personally, as has many long time VB(visual basic) programmers, I find VB.NET is no better than VB6, AND has a learning curve many VB'ers don't feel is worth it.

VB has always been kind of the stepchild when it comes to programming languages. Most "hard core programmers" believe it's too fat and has limited abilities. Both are true to a certain extent, but really the hate for VB comes from it's user friendly interface. You would think programmers would embrace an easier to understand and use language, but I guess it's like making a car any backyard mechanic can work on. It's hated by mechanics that make a living off of your car.

So much for explaining the redheaded stepchild, now let look at the "new and improved" stepchild. VB.NET

Many old VB'ers, including myself, was pumped about finally getting a completely revamped VB. Most were let down to say the least. VB.NET has all the same drawbacks as the old VB, plus it's lost it's user friendly interface forcing programmers to start all over. Lets face it, If I'm going to learn programming all over again, I might as well learn C+ or machine language.

VB's biggest downside has been requiring support libraries. Having to add additional libraries(DLL's/OCX's) and the added code necessary to support a more user friendly front end, make for a large install and a large executable when compiled. Or what is referred to as being "fat."

With C language, because Windows was programmed in C, all you need do is put together some nice slim code calling the support libraries already in Windows, and you have a quick running small application that doesn't take much memory(because the DLL's/OCX's all already in Windows memory), and very portable. Heck you can email the executable to someone and they don't need to install the program.

Another downside in VB was speed. Because VB does not communicate directly with "core components" it's overhead makes it slower. For example, VB cannot communicate directly with a COM port because the Windows library has control over it. What VB must do is use the Windows library as a 3rd party device for communication. VB sends a request to the Windows COM port driver(DLL/OCX/Library) which then passes the request to the COM port. Then the COM port send a response back to the Windows driver which send it back to the VB application. One of the reasons VB6 users are reluctant to give up VB6 is that just recently a 3rd party vendor has written some libraries that allow VB6 to communicate directly with a PC's hardware making it much faster. VB.NET does not have it.

Well VB.NET still requires the same support libraries. Remember when you needed to install, and still update, your DOTNET framework? Yup, still need all that fat. The old VB'ers are kind of bucking the system and refusing to upgrade to VB.NET. Microsoft has threatened to pull the plug on VB6, but there are already 3rd party vendors ready to take up were Microsoft leaves off.

Although VB6 is not without it's faults, there is a very good reason it has the support it does. VB6 is the king of RAD(rapid application development). People were getting tired of the 3 month wait while the old timer programmers hacked out some simple database application. And because of the 3 months they were quite happy to charge a hefty $30,000 price. Enter VB1. I started programming in VB roughly 12 years ago with Visual Basic version 1 and have used it through the current VB version 6. I even tried the VB.NET that was offered for free to current VB6 users, but it sucked.

I can pump out a complete database application in 5 minutes in VB, Try that with ANY other programming language.

Years ago one of our departments asked for some help with their DOS based program that kept crashing and killing the information in the database. pfft... DBase, what do you expect! It was a program they had spent about $30,000 on that was crap. I offered to write a Windows version and did it in 1 day. They used that program for 7 years and never had issues. VB is still the king of RAD, and you have much lower price to pay now for applications thanks to those VB programmers that crashed the "good thing" the old programmers had going.