I hate VB.NET
-
I hate it, I want to pretend it does not exist. It is giving me stress I have never had in my life! Yeeeeeeeeeeeeeeeeeaaaaaaaaaarrrrrrrrrggggggggggggggghhhhhhhhhh. Why are people even thinking of going to VB.NET? They say "ooohhh, I know VB or VBScript so it is going to be a cake walk doing this .NET stuff." Hah! Hah! I am the .NET guy here (C#) and we had to fix up a ".NET project" the other day. It was written in VB.NET. I stared at it for hours and got nowhere. I know VB, I know VBScript. I do not know VB.NET. VB.NET has the same syntax ideas, but is not the same thing. Simple stupid stuff like in C# you do namespaces properly or it does not work. In VB.NET, you can put them all over the show, or not at all, and with a big project it just bites trying to fix a namespace issue when you are thinking in C#. I mean
Dim exema as Exema = new ExemaWTF? Yet so many daft buggers are being fooled by this MS marketing rubbish that says if you know VB then you can do VB.NET easily. MS just made VB.NET to fool people, I swear, it is true. They made it so VB people would think .NET is easy, that their VB skills would help. Pfffff! Hah! Bill Sergio makes more sense. And C# is just so, so, so much better (leave C++ out of this ok?) *sigh* and it looks like because of the fooled available talent pool we are going to standardise on VB.NET... which will die one of these short days once MS has wooed enough of us into .NET. Then we will have to go to C#, which I want to do straight away. Please, any UK or South African developers, phone up my boss and shout C# down the line, please? Tell him that yes C# actually is being taken up and is better than VB.NET and there will be normal (not guru) developers using it. I am no guru and I am doing C#, but people think the normal devs do VB.NET and the gurus do C#. WTF? I am just very frustrated. This is a short term decision which is going to give me gray hairs in the long run. I hatesssssssss it. p.s. Not saying VB is bad. VB has it's place. But VB.NET does not. Different things. So don't go replying with "We told you VB sucked." Or I may just surgicaly implant a day old McDonalds burger in your spleen, no offense of course. :)Paul Watson
Bluegrass
Cape Town, South Africalauren wrote: theyre
Paul Watson wrote: I hatesssssssss it. "Gollum, gollum...." :laugh: Paul Watson wrote: Dim exema as Exema = new Exema :wtf: Surely he should be working at McD's? Paul Watson wrote: This is a short term decision which is going to give me gray hairs in the long run. It's Friday - get down to the waterfront and party instead :jig:
A pack of geeks, pale and skinny, feeling a bit pumped and macho after a morning of strenuous mouse clicking and dragging, arriving en masse at the gym. They carefully reset the machines to the lowest settings, offer to spot for each other on the 5 lb dumbells, and rediscover the art of macrame while attempting to jump rope. -Roger Wright on my colleagues and I going to gym each day at lunch
-
Paul Watson wrote: I hatesssssssss it. "Gollum, gollum...." :laugh: Paul Watson wrote: Dim exema as Exema = new Exema :wtf: Surely he should be working at McD's? Paul Watson wrote: This is a short term decision which is going to give me gray hairs in the long run. It's Friday - get down to the waterfront and party instead :jig:
A pack of geeks, pale and skinny, feeling a bit pumped and macho after a morning of strenuous mouse clicking and dragging, arriving en masse at the gym. They carefully reset the machines to the lowest settings, offer to spot for each other on the 5 lb dumbells, and rediscover the art of macrame while attempting to jump rope. -Roger Wright on my colleagues and I going to gym each day at lunch
Megan Forbes wrote: Surely he should be working at McD's? LOL, ok I made up the exema bit, but the syntax is correct.
Dim xmlwriterNew as XmlWriter = new XmlWriterMegan Forbes wrote: "Gollum, gollum...." hehe, exactly. I feel as conflicted as him right now.Paul Watson
Bluegrass
Cape Town, South Africalauren wrote: theyre making a movie about me "confessions of a dangerous bitch" (hey! she said it, not me)
-
I hate it, I want to pretend it does not exist. It is giving me stress I have never had in my life! Yeeeeeeeeeeeeeeeeeaaaaaaaaaarrrrrrrrrggggggggggggggghhhhhhhhhh. Why are people even thinking of going to VB.NET? They say "ooohhh, I know VB or VBScript so it is going to be a cake walk doing this .NET stuff." Hah! Hah! I am the .NET guy here (C#) and we had to fix up a ".NET project" the other day. It was written in VB.NET. I stared at it for hours and got nowhere. I know VB, I know VBScript. I do not know VB.NET. VB.NET has the same syntax ideas, but is not the same thing. Simple stupid stuff like in C# you do namespaces properly or it does not work. In VB.NET, you can put them all over the show, or not at all, and with a big project it just bites trying to fix a namespace issue when you are thinking in C#. I mean
Dim exema as Exema = new ExemaWTF? Yet so many daft buggers are being fooled by this MS marketing rubbish that says if you know VB then you can do VB.NET easily. MS just made VB.NET to fool people, I swear, it is true. They made it so VB people would think .NET is easy, that their VB skills would help. Pfffff! Hah! Bill Sergio makes more sense. And C# is just so, so, so much better (leave C++ out of this ok?) *sigh* and it looks like because of the fooled available talent pool we are going to standardise on VB.NET... which will die one of these short days once MS has wooed enough of us into .NET. Then we will have to go to C#, which I want to do straight away. Please, any UK or South African developers, phone up my boss and shout C# down the line, please? Tell him that yes C# actually is being taken up and is better than VB.NET and there will be normal (not guru) developers using it. I am no guru and I am doing C#, but people think the normal devs do VB.NET and the gurus do C#. WTF? I am just very frustrated. This is a short term decision which is going to give me gray hairs in the long run. I hatesssssssss it. p.s. Not saying VB is bad. VB has it's place. But VB.NET does not. Different things. So don't go replying with "We told you VB sucked." Or I may just surgicaly implant a day old McDonalds burger in your spleen, no offense of course. :)Paul Watson
Bluegrass
Cape Town, South Africalauren wrote: theyre
With you all the way, Paul. My first foray into .NET was VB.NET, everything since has been C#. It almost seems to me like they came up with VB.NET first, intending to head towards a Java-like (am I allowed to say that? ;P) version later. Then they started on C# and kept coming up with good ideas but never transfered them back to VB.NET. Does that make sense? Like VB.NET was never finished once they realised most people would go C# in the end anyway? Another example you didn't mention: is there a VB.NET equivalent to "using"? (the inline using that Disposes of things for you, not the one that references things) The using construct is just about the most useful thing in C#. You can rely on data exceptions to throw you out of a piece of code without having to catch it and dispose of the Adapters/Connections or risk leaving your database locked. (just one example of its usefulness) I hatesss VB.NET too. Paul Pleasently caving in, I come undone - Queens of the Stone Age, No One Knows
-
I hate it, I want to pretend it does not exist. It is giving me stress I have never had in my life! Yeeeeeeeeeeeeeeeeeaaaaaaaaaarrrrrrrrrggggggggggggggghhhhhhhhhh. Why are people even thinking of going to VB.NET? They say "ooohhh, I know VB or VBScript so it is going to be a cake walk doing this .NET stuff." Hah! Hah! I am the .NET guy here (C#) and we had to fix up a ".NET project" the other day. It was written in VB.NET. I stared at it for hours and got nowhere. I know VB, I know VBScript. I do not know VB.NET. VB.NET has the same syntax ideas, but is not the same thing. Simple stupid stuff like in C# you do namespaces properly or it does not work. In VB.NET, you can put them all over the show, or not at all, and with a big project it just bites trying to fix a namespace issue when you are thinking in C#. I mean
Dim exema as Exema = new ExemaWTF? Yet so many daft buggers are being fooled by this MS marketing rubbish that says if you know VB then you can do VB.NET easily. MS just made VB.NET to fool people, I swear, it is true. They made it so VB people would think .NET is easy, that their VB skills would help. Pfffff! Hah! Bill Sergio makes more sense. And C# is just so, so, so much better (leave C++ out of this ok?) *sigh* and it looks like because of the fooled available talent pool we are going to standardise on VB.NET... which will die one of these short days once MS has wooed enough of us into .NET. Then we will have to go to C#, which I want to do straight away. Please, any UK or South African developers, phone up my boss and shout C# down the line, please? Tell him that yes C# actually is being taken up and is better than VB.NET and there will be normal (not guru) developers using it. I am no guru and I am doing C#, but people think the normal devs do VB.NET and the gurus do C#. WTF? I am just very frustrated. This is a short term decision which is going to give me gray hairs in the long run. I hatesssssssss it. p.s. Not saying VB is bad. VB has it's place. But VB.NET does not. Different things. So don't go replying with "We told you VB sucked." Or I may just surgicaly implant a day old McDonalds burger in your spleen, no offense of course. :)Paul Watson
Bluegrass
Cape Town, South Africalauren wrote: theyre
-
With you all the way, Paul. My first foray into .NET was VB.NET, everything since has been C#. It almost seems to me like they came up with VB.NET first, intending to head towards a Java-like (am I allowed to say that? ;P) version later. Then they started on C# and kept coming up with good ideas but never transfered them back to VB.NET. Does that make sense? Like VB.NET was never finished once they realised most people would go C# in the end anyway? Another example you didn't mention: is there a VB.NET equivalent to "using"? (the inline using that Disposes of things for you, not the one that references things) The using construct is just about the most useful thing in C#. You can rely on data exceptions to throw you out of a piece of code without having to catch it and dispose of the Adapters/Connections or risk leaving your database locked. (just one example of its usefulness) I hatesss VB.NET too. Paul Pleasently caving in, I come undone - Queens of the Stone Age, No One Knows
Paul Riley wrote: is there a VB.NET equivalent to "using"? Yup, it's a hack (surprise, surprise) involving a try/finally block. X| VB.NET is the devil and the sooner more people realise that, the better off everyone will be. Thanks, Paul. :jig: Cheers, Simon "The day I swan around in expensive suits is the day I hope someone puts a bullet in my head.", Chris Carter. animation mechanics in SVG
-
Paul Riley wrote: is there a VB.NET equivalent to "using"? Yup, it's a hack (surprise, surprise) involving a try/finally block. X| VB.NET is the devil and the sooner more people realise that, the better off everyone will be. Thanks, Paul. :jig: Cheers, Simon "The day I swan around in expensive suits is the day I hope someone puts a bullet in my head.", Chris Carter. animation mechanics in SVG
SimonS wrote: Yup, it's a hack (surprise, surprise) involving a try/finally block. :rolleyes: So... no then? ;P SimonS wrote: VB.NET is the devil and the sooner more people realise that, the better off everyone will be. :laugh: If this isn't crying out for someone to claim it as a sig, I don't know what is. Paul Pleasently caving in, I come undone - Queens of the Stone Age, No One Knows
-
David. I don't think he actually meant it. ;P
Hey, what can I say? I'm a chick magnet...a babe conductor...a logarithm for the ladies. -Strong Bad from HomeStarRunner.com Essential Tips for Web Developers
-
I hate it, I want to pretend it does not exist. It is giving me stress I have never had in my life! Yeeeeeeeeeeeeeeeeeaaaaaaaaaarrrrrrrrrggggggggggggggghhhhhhhhhh. Why are people even thinking of going to VB.NET? They say "ooohhh, I know VB or VBScript so it is going to be a cake walk doing this .NET stuff." Hah! Hah! I am the .NET guy here (C#) and we had to fix up a ".NET project" the other day. It was written in VB.NET. I stared at it for hours and got nowhere. I know VB, I know VBScript. I do not know VB.NET. VB.NET has the same syntax ideas, but is not the same thing. Simple stupid stuff like in C# you do namespaces properly or it does not work. In VB.NET, you can put them all over the show, or not at all, and with a big project it just bites trying to fix a namespace issue when you are thinking in C#. I mean
Dim exema as Exema = new ExemaWTF? Yet so many daft buggers are being fooled by this MS marketing rubbish that says if you know VB then you can do VB.NET easily. MS just made VB.NET to fool people, I swear, it is true. They made it so VB people would think .NET is easy, that their VB skills would help. Pfffff! Hah! Bill Sergio makes more sense. And C# is just so, so, so much better (leave C++ out of this ok?) *sigh* and it looks like because of the fooled available talent pool we are going to standardise on VB.NET... which will die one of these short days once MS has wooed enough of us into .NET. Then we will have to go to C#, which I want to do straight away. Please, any UK or South African developers, phone up my boss and shout C# down the line, please? Tell him that yes C# actually is being taken up and is better than VB.NET and there will be normal (not guru) developers using it. I am no guru and I am doing C#, but people think the normal devs do VB.NET and the gurus do C#. WTF? I am just very frustrated. This is a short term decision which is going to give me gray hairs in the long run. I hatesssssssss it. p.s. Not saying VB is bad. VB has it's place. But VB.NET does not. Different things. So don't go replying with "We told you VB sucked." Or I may just surgicaly implant a day old McDonalds burger in your spleen, no offense of course. :)Paul Watson
Bluegrass
Cape Town, South Africalauren wrote: theyre
Paul Watson wrote: Not saying VB is bad. VB has it's place. But VB.NET does not. Different things. So don't go replying with "We told you VB sucked." LOL - that's great. So the conversation we planned together did not go well then ? Christian No offense, but I don't really want to encourage the creation of another VB developer. - Larry Antram 22 Oct 2002
C# will attract all comers, where VB is for IT Journalists and managers - Michael P Butler 05-12-2002
Again, you can screw up a C/C++ program just as easily as a VB program. OK, maybe not as easily, but it's certainly doable. - Jamie Nordmeyer - 15-Nov-2002 -
David. I don't think he actually meant it. ;P
Hey, what can I say? I'm a chick magnet...a babe conductor...a logarithm for the ladies. -Strong Bad from HomeStarRunner.com Essential Tips for Web Developers
I think we should dig up Paul's Boss's number & give him a call anyway though, just to make sure - leaving a VB user to suffer like that is just too cruel.
---
Shog9 The siren sings a lonely song - of all the wants and hungers The lust of love a brute desire - the ledge of life goes under
-
I hate it, I want to pretend it does not exist. It is giving me stress I have never had in my life! Yeeeeeeeeeeeeeeeeeaaaaaaaaaarrrrrrrrrggggggggggggggghhhhhhhhhh. Why are people even thinking of going to VB.NET? They say "ooohhh, I know VB or VBScript so it is going to be a cake walk doing this .NET stuff." Hah! Hah! I am the .NET guy here (C#) and we had to fix up a ".NET project" the other day. It was written in VB.NET. I stared at it for hours and got nowhere. I know VB, I know VBScript. I do not know VB.NET. VB.NET has the same syntax ideas, but is not the same thing. Simple stupid stuff like in C# you do namespaces properly or it does not work. In VB.NET, you can put them all over the show, or not at all, and with a big project it just bites trying to fix a namespace issue when you are thinking in C#. I mean
Dim exema as Exema = new ExemaWTF? Yet so many daft buggers are being fooled by this MS marketing rubbish that says if you know VB then you can do VB.NET easily. MS just made VB.NET to fool people, I swear, it is true. They made it so VB people would think .NET is easy, that their VB skills would help. Pfffff! Hah! Bill Sergio makes more sense. And C# is just so, so, so much better (leave C++ out of this ok?) *sigh* and it looks like because of the fooled available talent pool we are going to standardise on VB.NET... which will die one of these short days once MS has wooed enough of us into .NET. Then we will have to go to C#, which I want to do straight away. Please, any UK or South African developers, phone up my boss and shout C# down the line, please? Tell him that yes C# actually is being taken up and is better than VB.NET and there will be normal (not guru) developers using it. I am no guru and I am doing C#, but people think the normal devs do VB.NET and the gurus do C#. WTF? I am just very frustrated. This is a short term decision which is going to give me gray hairs in the long run. I hatesssssssss it. p.s. Not saying VB is bad. VB has it's place. But VB.NET does not. Different things. So don't go replying with "We told you VB sucked." Or I may just surgicaly implant a day old McDonalds burger in your spleen, no offense of course. :)Paul Watson
Bluegrass
Cape Town, South Africalauren wrote: theyre