I hate to get involved at all, but…


color=teal>There have been a few VB vs C# debates flying around… I’ll refrain
from linking to them all, as they aren’t really saying anything new. One comment
in particular caught my eye though, and I have to
respond.


color=teal> 


color=teal>Jesse
Ezell’s post
includes a quote that says “Microsoft is standardizing on C#”
and then goes on to use that quote as a reason to suggest you shouldn’t use
VB.NET… well, I work for Microsoft and I am in discussions with the .NET
groups every day and I know exactly what we are working on and working with, and
I can tell you that Microsoft is not “standardizing” on anything. style="mso-spacerun: yes">   Yes, much of our internal .NET
development is done with C#, and why not? We are a huge campus full of C++
developers. If we did standardize on anything, I would expect it to be Managed
C++.  Also, it’s worth pointing out
that we do development in VB as well, including some of our internal business
applications.


color=teal> 


color=teal>Before .NET, Microsoft used C++ almost exclusively (and we still do
almost everything in C++) but that doesn’t mean that everyone should use C++ to
build their line of business applications. People also point out that much of
the Framework was written in C#, but remember, it was written by C++ developers.
There isn’t a single class, method, property, or event, anywhere in the
Framework, that you can’t use from VB.NET. If someone builds a library in C#
that you can’t use from VB.NET, (and vice versa) they probably did it wrong…


color=teal> 


color=teal>C# is the flashy new language that has arrived with .NET so it gets a
lot of attention (which led to more samples being written in C#, etc…), but
Visual Basic is by far the more popular language and I don’t expect that to
change. I write code in Visual Basic everyday and nothing in the Framework is
being “hidden” from me, I have full access to the Framework in all its glory. I
don’t think there is any need to ignore C#, but you certainly don’t have to
learn it to work in .NET…


color=teal> 


color=teal>Stop debating this issue; pick a language and build something…
you’ll feel better.


Comments (8)

  1. Anonymous says:

    Duncan speaks “I hate to get involved at all, but…” : Cory Smith Blog

  2. Sam says:

    Stop it. Don’t do this.

  3. Jesse Ezell says:

    I took the quote from the newsgroup posting to be referring to the fact that MS has currently only standardized C# with ECMA, etc. out of the .NET languages (perhaps this was not what it was referring to after hearing your take on it).

    In any case, the point of what I was saying was not that C# is superior to VB from a features standpoint or that MS is only going to be using C# for all its dev projects, but that C# is becoming a defacto standard in the community, so for that reason alone it is a very good idea to at least be familiar with C# (whether or not you code in or prefer Delphi, Eiffel, CAML, X#, VB, J#, etc.). Regardless, MS and .NET still rock!

    What messes we get ourselves into by opening our big mouths… I really do think Dostoevsky was onto something (http://dotnetweblogs.com/Jezell/posts/4552.aspx).

  4. Sam Gentile says:

    Yes, thanks Duncan on clearing up what goes on internally. As I said in our emails, I meant my original "Stop it" not at you but the people continuing this senseless debate. As I said there, "Yes, sorry, responded to the wrong person. We (Scott and I) wanted to stop this senseless stuff from happening again. I have seen it a million times in my last 3 years with .NET/NGWS, inside and outside the borg. It is a waste of time and takes out communities.

    Sorry, I just want this community not to go the way of C# Corner and other now low-signal communities. It wasn’t directed at you personally.

  5. Ron Green says:

    What’s really sad is I am learning C# now because my company has decided that VB is just a toy language and anyone who writes VB is not really a programmer. I was eventually going to learn C# anyway, but because I wanted to expand my knowledge not because someone has decided my language of choice is not good enough. I sometimes wish MS has rename VB.net something else like B# so at least some of these people might stop and actually look at the language before passing judgement.

  6. Good comments. I agree, pick a language, write some code, have some fun, stop the debates.

  7. Lubos says:

    Well said Duncan! This debate has been going on as long as I can remember. I guess the positive in this is that we are all passionate about the same thing – .NET!