VB.NET or C#

Heath Stewart

He never made such a comment, but was stating that which language you use a matter of preference. True, VB.NET and C# generate almost the same MSIL (C# does support more features of the CLI, however, and does optimize slightly better in some cases), but a developer as he said will most likely use whichever language he has more experience (with similar) languages. Yes, I do believe that VB sucks (because I know how it works based on my decade of experience with OLE automation and COM) but I have not such opinion of VB.NET other than that I personally don't like the syntax. Coming from a long background with C/C++, Perl, and Java I like curly braces and semi-colons, but it's only my personal opinion, which is what the poster said is all you're offering and it's true. What you stated is your opinion and nothing more. And that's okay, just don't think it's a matter of fact.

Microsoft MVP, Visual C# My Articles

Stefan Troschuetz

But want did you want to achieve? Do you want to hear that VB.NET is the greatest language ever. ;) Why do you bother what others think about the language you use. In my opinion everybody should use what he or she can handle best. I don't like some languages too or think it's hard to use them. But i don't care if anybody else use it and thinks it's really great. It's pretty sad that some have a snobbish behaviour, as you described it so nice, or think that VB.Net sucks. But that's life. There will always be some unteachable people. This is as sure as there will always be the quarrel which is the better operating system: Windows or Linux. But that's another story ;) So don't bother and lets not waste our time with this dumb and aimless discussion!

Serge Lobko Lobanovsky

Heath Stewart wrote: He never made such a comment, but was stating that which language you use a matter of preference. Actually, I was not referring Colin when put this. . What you stated is your opinion and nothing more. Well, my opinion is based on personal experience in working with C# programmers. As you can see in my first post, I state that there is snobbery in C# programmers. I just simply don't understand why you (C# programmers) underestimate our (VB.NET) ability to create reliable and scalable software. It proved to be a stereotype that VB.NET sucks because VB sucks. I want to break this vicious circle. Regards, Serge (Logic Software)

Serge Lobko Lobanovsky

Stefan Troschütz wrote: Do you want to hear that VB.NET is the greatest language ever. Why do you bother what others think about the language you use. ;-) No, to me it really doesn't matter what language people in my team is using as long as the code they create works as it is supposed to. Actually, I don't bother what people say about VB.NET. I bother what they think of the products which are written in it. So don't bother and lets not waste our time with this dumb and aimless discussion! As long as there "unteachable" people, there will be place for a "teaching" discussion, you can be sure! ;-) Regards, Serge (Logic Software)

Heath Stewart

Except in most cases VB.NET programmers are VB programmers, which typically don't understand one iota about true development since VB hides so much in the runtime implementation that things like good class design and performance are easily excused. VB was created to make programming easier for a target audience that probably should've stayed with their jobs at McD's (extreme case, but that's how I typically see so many people jumping into this field). You and others may be exceptions, but that's were the snobbery stems.

Microsoft MVP, Visual C# My Articles

scadaguy

Daniel Turini wrote: I'm yet to see a pure VB programmer who clearly knows where to use and can differ a mutex, a semaphore or an event. Or who can spot a race condition or a deadlock. Pure C# programmers aren't much better. In fact, the majority of code I see that uses the more advanced multithreaded techniques is flawed, sometimes in significant ways. :(

Daniel Turini

Serge Lobko-Lobanovsky wrote: I just simply don't understand why you (C# programmers) underestimate our (VB.NET) ability to create reliable and scalable software. Ok, just compare at the posts on CodeProject's VB forum, on C# and on C++ and you'll understand why this happen. It's useful to remember that the "B" on BASIC stands for "Beginners"; BASIC = Beginners All-purpose Symbolic Instruction Code. Due to technical difficulties my previous signature, "I see dumb people" will be off until further notice. Too many people were thinking I was talking about them... :sigh:

Andy Brummer

I've found an overwhelming need for new C# and VB developers to rush headlong to the System.Threading namespace just so they can feel cool by typing new Thread. I've learned a great appreciation for the delegate.beginInvoke method since it covers 90% of the cases when I need to run on a different thread. And it is much easier to use since you can just pass parameters to a function.

If you don't kill me you will only make me stronger That and a cup of coffee will get you 2 cups of coffee

Stefan Troschuetz

Then good luck on your "teaching" mission. I think you've found yourself a lifetime task :)

Serge Lobko Lobanovsky

Daniel Turini wrote: Ok, just compare at the posts on CodeProject's VB forum, on C# and on C++ and you'll understand why this happen. That's what I had been doing when I got your reply. I found out that it would be much more useful for me to sit on these forums than of VB.NET ones. I do understand now your position in this argument. It's useful to remember that the "B" on BASIC stands for "Beginners"; BASIC = Beginners All-purpose Symbolic Instruction Code. However, with dot NET we can use VB.NET as well ;-) Regards, Serge (Logic Software)