Linked by Thom Holwerda on Mon 11th Jun 2012 00:38 UTC, submitted by judgen
Windows "Microsoft recently extended 'It Just Works' compatibility for Visual Basic 6 applications through the full lifetime of Windows 8. Visual Basic 6 first shipped in 1998, so its apps will have at least 24 years of supported lifetime. Contrast that with the Microsoft .NET Framework 1.0 (2002), which is incompatible with Windows 7 (2009)."
Thread beginning with comment 521585
To read all comments associated with this story, please click here.
Why the hate?
by Gullible Jones on Mon 11th Jun 2012 18:58 UTC
Gullible Jones
Member since:
2006-05-23

First of all, a disclaimer... I have never used Visual Basic 6. I learned some Basic on a legacy Mac about a decade ago, and quickly forgot all of it. Right now I know smatterings of several languages, Java probably being my strongest. If you told me to do some task in VB6, I wouldn't have a clue how.

However.

I've noticed an attitude among computer enthusiasts that, if X is easy to use, X must suck. It's true that power and versatility often imply a steep learning curve; but I don't think they necessarily have to, and furthermore, not everything needs to be as powerful and versatile as C. Sometimes you want to use the right tool for the job.

e.g. A small program for manipulating text might be more efficient if written in C, but you can do it in Perl or shell script with a tenth the effort. Or a GUI for some program could be written using GTK+ and C, but if memory use is not an issue, using PyGTK could make it more maintainable.

Couldn't the same be considered to apply to small graphical programs for Windows? Maybe VB6 is the right tool for quickly throwing together something that doesn't require power, finesse, or portability.

OTOH, I did look into GAMBAS once, and found the syntax completely inscrutable. If VB6 looks like that I can understand why it would be disliked.

Reply Score: 4

RE: Why the hate?
by Tuishimi on Mon 11th Jun 2012 19:28 in reply to "Why the hate?"
Tuishimi Member since:
2005-07-06


e.g. A small program for manipulating text might be more efficient if written in C, but you can do it in Perl or shell script with a tenth the effort. Or a GUI for some program could be written using GTK+ and C, but if memory use is not an issue, using PyGTK could make it more maintainable.


I agree. It really depends on what you are trying to do and how much time you have to do it in. Prototyping in some of the interpreted/dynamic languages is useful too...

Reply Parent Score: 3

RE: Why the hate?
by Delgarde on Tue 12th Jun 2012 01:40 in reply to "Why the hate?"
Delgarde Member since:
2008-08-19

Couldn't the same be considered to apply to small graphical programs for Windows? Maybe VB6 is the right tool for quickly throwing together something that doesn't require power, finesse, or portability.


The problem with that reasoning is that over time, small programs often become large programs. And then when you find that you *do* need power, and you *do* need finesse and you *do* need portability, what do you do?

Reply Parent Score: 4