Making an Argument Against Using Visual-Basic?

ethan_clark asks: "I work for a small company (< 10 employees) as a software engineer. The company got its start with a software product written by the owner in VisualBasic. He hired me to assist in rewriting the software – only catch is, he's stuck on having it re-written in VisualBasic. This scares me, but I honestly can't make a good argument against VB because I'm not familiar enough with it. So my question is twofold: I am looking for some confirmation to my suspicion that VB isn't the greatest language for large projects; and If VB isn't good, arguments against using it. If it is good, what arguments would you use to argue for it (for my sake)?" If you are going to argue against a language, it is best if you do so after you become familiar with it so that you can argue fairly on its merits and deficiencies. VisualBasic, like just about every other language, has its place. For the sake of discussion however, what tasks would VisualBasic not be suited for?

Comments

Re:It does have it's place too

[Jesus_666]

True. VB has one strength: Convenient interface development. No other language/GUI toolkit I know has that.

With Java/Swing you have NetBeans which sometimes does what you want and only accasionally completely screws up the form you're working on. I don't know about SWT.
With C++/WxWidgets you get WxGlade which I have never seen actually working. C++/FLTK gives you Fluid, which works most of the time but has always given me problems when working on programs that don't fit in a single file. The Qt RAD tool appears to work, but I haven'tspent much time with it so far.

VB isn't that great a language, but it's really nice for putting together GUIs.