Why I Hate VB Today
-
Don't forget the craptastic, "You have to actually tell the compiler to shortcut boolean logic with AndAlso and OrElse." Also that you have to call a method Function or Sub depending whether it returns something (or not). When I took my current position, I thought, "It's the problems that make the work interesting, and the language won't bother me too much." By now, I'm out looking for something in C#.
Had to ask you about your user ID. Are you a golden retriever fan?
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
Well, don't use it then. Duh!
Easy to say when you're free to look for other work. For reasons I've already gone over, I don't have that option until late next year.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
Yep, VB3 was great (I never used VB1 or 2)... Before then, I had stuck to console programming because... Let's face it... I was lazy. Then VB4 came along, and that was great... Then VB5 came along, finally adding OOP (Kinda... Well, almost... Eh) Then VB6 came along, and I started to wonder. Then VB.NET came along, and I cheered. Then I looked over at C#, and thought, "Why am I still writing VB code?"
Proud to have finally moved to the A-Ark. Which one are you in?
Author of the Guardians Saga (Sci-Fi/Fantasy novels) -
- The intellisense refuses to "let go" unless I tap the Escape key 1) Syntax highlighting sucks. In C#, all types are highlighted - in VB, only intrinisc types are highlighted. 2) It's VB. 3) There are no automatic code formatting options like we get with C#
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
In the other languages the programmers are more than happy to share information. With VB programmers everything is obscure and in some secret code. They act as if they are giving away national secrets if you ask them a question. The best way to show you are knowledgible is to share it. I share mine without any hassles or ridicule. If someome wants to learn I'm all in. VB programmers hide in the corner whispering so their secrets don't fall into the wrong hand. Sheesh!!!
The reason VB'ers don't share is because of people like you. We're afraid to reveal that we write in VB (and feel guilty that we like it).So If you ask us for a sample code, we may try to quickly convert it to C#. But then you would find us out because we would inevitably make a syntax error.
-
The reason VB'ers don't share is because of people like you. We're afraid to reveal that we write in VB (and feel guilty that we like it).So If you ask us for a sample code, we may try to quickly convert it to C#. But then you would find us out because we would inevitably make a syntax error.
Actually, that is the best answer I have ever gotten :)
-
Yep, VB3 was great (I never used VB1 or 2)... Before then, I had stuck to console programming because... Let's face it... I was lazy. Then VB4 came along, and that was great... Then VB5 came along, finally adding OOP (Kinda... Well, almost... Eh) Then VB6 came along, and I started to wonder. Then VB.NET came along, and I cheered. Then I looked over at C#, and thought, "Why am I still writing VB code?"
Proud to have finally moved to the A-Ark. Which one are you in?
Author of the Guardians Saga (Sci-Fi/Fantasy novels)Microsoft should have just called C# "VB7" and never invented VB.NET. Old school VB programmers like myself would have naturally moved to the new "C-style" VB language long ago, and we would all be better off. Why they would keep perpetuating this duality of quality on the same framework I have no idea...
-
Go steady. VB was the first tool I used that let me drag and drop buttons, etc. onto a form -- without slogging for huge lengths of time writing either the form or the objects to drop on it. That's a fond memory -- especially now that the GUIs here are done with (%#@&ing) swing.
I wanna be a eunuchs developer! Pass me a bread knife!
-
unsigned bullet = 4;
for (;;)
{
printf("%d) It\'s not C++.\n",bullet++);
}Software Zen:
delete this;Gary Wheeler, Is your code in Visual Basic? No Visual Basic up to VB 6 was good, but VBA and VBScript are completely different languages in my opinion. I must be the only one here that likes Visual Basic. But have never got round to learning VBA and try not to use VBScript as Netscape and some other browsers still don't support it.
-
C# is the VB for developers that enjoy writing .NET code using the (arcane) C/C++ syntax! Just let it go and enjoy your preferred language.
1.) I don't try and be an expert in every language so I picked one and VB was the one I chose. 2.) I can use VBA in many other applications like MS Excel, AutoCAD, and others with ease. 3.) I can use VBA in Automation HMI projects which is the standard and not C,C#, or other C types. 4.) It is quick to use since I am fluent in VB6, VB.NET, VBScript, VBA. 5.) I does what I need it to do why force myself to learn C# more than I know now I rather learn LISP if I have to work with parenthses and extra characters for line terminations and wrapping. I suggest everyone just pick a language and use it. If it doesn't accomplish what you want and C#, C++, HTML, JScript, Java, LISP, or any other language does then learn and use it. It's about the project not what language one uses.