Quote:Original post by daviangel
#1 Microsoft treats VB.NET as a second class language compared to C# i.e. no XNA support, documentation/code lacking in many other areas not even related to XNA, etc.
There's plenty of resources available for VB.Net. Most examples in the MSDN documentation are written in both C# and VB, and there are a lot of books available that target VB exclusively. C# might be a slightly more popular, and doesn't make VB an irrelevant language.
Quote:#2 It makes you lazy. Seriously I know get all the advice the C language based programmers used to give to avoid it if possible or as Charles Petzold would say VB rots the brain or something like that. You can type all your code with total disregard to case since VB is case insensitive first of all. So you get in the bad habit of not capitalizing anything since the IDE will do it for you. That brings me to the second point which is intellisense and code snippets is ages ahead in VB.NET compared to C# so that's the other part that makes you lazy so when you do switch to C++ or C# it'll make you made because it's those little things that will aggravate you.
So the superior support for VB.Net is a bad thing? Well, I guess you can always write your VB code in notepad and compile using the command line if that makes you less 'lazy'.