Re:Why I am called "the Father of Visual Basic" (1996)
by cm2187 on Thursday March 19, 2015 @07:24PM
(#9235261)
Not sure I follow your point. You can write really bad C#. And you can write even worse c++. The quality of a language isn't about how bad you can twist it if you decide to be reckless.
In fact I must say one of the things that I appreciate the most about VB, beside case insensitivity is the IDE. I think c# is catching up now but the VB IDE is incredible in term of how much help you get, immediate feedback on what went wrong, rich auto-completion of code.
Re:Why I am called "the Father of Visual Basic" (1996)
by jimmaswell on Friday March 20, 2015 @07:28AM
(#9237037)
The code completion is just as good or better for c# from my experience
VB.Net is a horrible language that lets developers get away with some really awful practices. The fact that the various Options are still present, and not on by default, is a recipe for disaster. That this is legal:
Sub Main dim x as boolean = false ''or true... dim y as integer = 0
select case y case x Console.Write("What does this even equate to???") end select End Sub
end case
or that this is legal:
Yes, I dealt with code that had both of those "techniques" in it... ugh.The second example was mainly because the off shore coders didn't realise AddHandler/RemoveHandler existed... le sigh