Why I Hate VB Today
-
- 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- It's super odd array declaration syntax that allows indexing to start at 1 instead of 0. There are a couple of things it has that I wish C# had though. -1) Calling an interface implementation method by a different name. Thats handy some times when implementing 4 similar interfaces. -2) It's XML support in the code. It's nice sometimes. -3) How you don't have to check if a event handler is null before you call it. I don't think I've ever wanted calling a null event handler to throw an exception. Shoot me now, I can't believe I said something positive about VB.
-
- It's super odd array declaration syntax that allows indexing to start at 1 instead of 0. There are a couple of things it has that I wish C# had though. -1) Calling an interface implementation method by a different name. Thats handy some times when implementing 4 similar interfaces. -2) It's XML support in the code. It's nice sometimes. -3) How you don't have to check if a event handler is null before you call it. I don't think I've ever wanted calling a null event handler to throw an exception. Shoot me now, I can't believe I said something positive about VB.
Phil Martin... wrote:
-1) Calling an interface implementation method by a different name. Thats handy some times when implementing 4 similar interfaces.
But this seems to compile in C#...
public interface IFace1
{
void Func1();
}public interface IFace2
{
void Func1();
}class Class1 : IFace1, IFace2
{
void IFace1.Func1() { }void IFace2.Func1() { } void Func1() { }}
Phil Martin... wrote:
-2) It's XML support in the code. It's nice sometimes.
What does that mean?
Phil Martin... wrote:
-3) How you don't have to check if a event handler is null before you call it. I don't think I've ever wanted calling a null event handler to throw an exception.
I don't have that problem. When I create a custom event, I do this:
null.
.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 -
No, that's rule six...
1f y0u c4n r34d 7h15 y0u r3411y n33d 70 g37 14!d Gotta run; I've got people to do and things to see... Don't tell my folks I'm a computer programmer - They think I'm a piano player in a cat house... Da mihi sis crustum Etruscum cum omnibus in eo!
-
- 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, 2001Well, joke about VB all that you want, but if it pays your meals, then what the heck??? I'll take your VB jobs if you really don't want them...
1f y0u c4n r34d 7h15 y0u r3411y n33d 70 g37 14!d Gotta run; I've got people to do and things to see... Don't tell my folks I'm a computer programmer - They think I'm a piano player in a cat house... Da mihi sis crustum Etruscum cum omnibus in eo!
-
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)Ian Shlasko wrote:
Then I looked over at C#, and thought
Whereas I looked at c# and wondered why anyone would use a case sensitive language. It wasn't till intellisense improved to the point where case was irrelevant that I was willing to move to c# and that was in vs08.
Never underestimate the power of human stupidity RAH
-
Well, going back to C# on this project is a moot point because I got the app running late yesterday afternoon. Since the code is essentially at the same place we were on Veteran's Day with the C# version, why go back? The gist of that is that there will be no team meeting about what we should do. The customer called my boss into his office and shut the door this morning, so nobody else knows what was said. In essence, I'm in VB hell, and will be there until sometime late next year when/if the contract is converted to civil service. This is the fourth job I've had in the last three years, and don't want to hop to a new one until I've been here at least a year (March 2011).
.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, 2001I'm glad to hear your ass is not in the sling for your managers decisions.
John Simmons / outlaw programmer wrote:
This is the fourth job I've had in the last three years
I can understand that decision, economic survival has some excellent benefits. And no matter the reasons too many short term contracts just looks bad on a CV.
Never underestimate the power of human stupidity RAH
-
Phil Martin... wrote:
-1) Calling an interface implementation method by a different name. Thats handy some times when implementing 4 similar interfaces.
But this seems to compile in C#...
public interface IFace1
{
void Func1();
}public interface IFace2
{
void Func1();
}class Class1 : IFace1, IFace2
{
void IFace1.Func1() { }void IFace2.Func1() { } void Func1() { }}
Phil Martin... wrote:
-2) It's XML support in the code. It's nice sometimes.
What does that mean?
Phil Martin... wrote:
-3) How you don't have to check if a event handler is null before you call it. I don't think I've ever wanted calling a null event handler to throw an exception.
I don't have that problem. When I create a custom event, I do this:
null.
.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- Congratulations on writing code that will compile, but it isn't the same thing. 2) Here's a simple example: Dim xml =
Shrimp Cocktail Escargot Filet Mignon Garlic Potatoes Broccoli Chocolate Cheesecake
And it will create an XElement tree for use in code. Do a search for "XML Literals in VB.Net". You can do some nice subtitution and things as well. It's nice, sometimes. 3) I think something got trimmed in your third one, it just said "null".
-
- 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, 2001Funny - those all sound like problems with your VB IDE (granted, not a lot of options there), not the language itself. (Which has plenty of reasons to hate it).
-
- 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 -
Yeah the tension between the two is killing me - when is John finally going to show VB what a man he is? Will VB cry? Will they hold hands? And finally, the most important question: does VB have a sister?
¡El diablo está en mis pantalones! ¡Mire, mire! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! Personal 3D projects Just Say No to Web 2 Point Blow
I heard that VB has been getting more than a little familiar with her coach from Jimmy Connors' Pro Tennis Tour. Could be trouble waters ahead.
I wanna be a eunuchs developer! Pass me a bread knife!
-
Jim Crafton wrote:
does VB have a sister
Yes. Yes she does[^]!
Do Until True = False
Bump Squidgey bits
LoopHenry Minute Do not read medical books! You could die of a misprint. - Mark Twain Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.”
-
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) -
No, that's rule six...
1f y0u c4n r34d 7h15 y0u r3411y n33d 70 g37 14!d Gotta run; I've got people to do and things to see... Don't tell my folks I'm a computer programmer - They think I'm a piano player in a cat house... Da mihi sis crustum Etruscum cum omnibus in eo!
-
Ian Shlasko wrote:
Then I looked over at C#, and thought
Whereas I looked at c# and wondered why anyone would use a case sensitive language. It wasn't till intellisense improved to the point where case was irrelevant that I was willing to move to c# and that was in vs08.
Never underestimate the power of human stupidity RAH
-
The first letter doesn't start with a C. That is I love any syntax of a programming language that starts with a C.
"Program testing can be used to show the presence of bugs, but never to show their absence." << please vote!! >>
-
You love COBOL!!!???!!! Well, there's a first time for everything. OK, I'm kidding, I've met people who like COBOL. (Also, read about one in this thread.)
I was waiting for someone to point that out, ;-) ok, let me rephrase:
string language = getLanguage();
if ((language.Length < 4) &&
((language.StartsWith('C') == true) ||
(language.StartsWith('c') == true)))
{
MessageBox.Show("I like this shit!! ;-)");
}"Program testing can be used to show the presence of bugs, but never to show their absence." << please vote!! >>
-
I was waiting for someone to point that out, ;-) ok, let me rephrase:
string language = getLanguage();
if ((language.Length < 4) &&
((language.StartsWith('C') == true) ||
(language.StartsWith('c') == true)))
{
MessageBox.Show("I like this shit!! ;-)");
}"Program testing can be used to show the presence of bugs, but never to show their absence." << please vote!! >>
-
- 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 -
- Extra keywords... List(Of Integer) vs. List<int> 5) It's VB. 6) There is NOOOOOOO.... Rule 6 :)
Proud to have finally moved to the A-Ark. Which one are you in?
Author of the Guardians Saga (Sci-Fi/Fantasy novels)- There is Rule 6 8) Rule 6 is on Rule 9 9) It's VB 10) Option Explicit 11) Option Strict
-
Funny - those all sound like problems with your VB IDE (granted, not a lot of options there), not the language itself. (Which has plenty of reasons to hate it).
Such as?
