More VB fun

"They are not mutually exclusive.  We can co-exist.  There is plenty of room in the world for more than one language :-)  Also, as time moves forward, the two languages will diverge more... allowing for additional flexibility and capabilities.  You should know both; if nothing more than to take advantage of everyones knowledge... some being published in C# while others in VB.NET."
[Cory Smith]

A great concept, but unfortunately most people don't have enough spare time to become experts in multiple languages. Admittedly, anyone who has been around the block a few times should already know both, at least enough to read / understand code written in the other. The majority of the differences are just eye candy. Still, each language has a target audience and the kinds of apps you are creating will probably influence what language you are / should be using. VB is about solving problems quickly (hence VB had a lot better IDE support in V1.0 than C#). On the other hand, C# is about creating elegant solutions (hence C# code is more concise, especially when dealing with OO features like overloads or using the IDisposable interface). Of course, this doesn't mean that you can't create elegant solutions in VB, just that they might not be percieved as such--alas, perception is reality, so whether or not that is really the case really doesn't matter to 90% of the world, since they won't bother to do their homework.

But, if you are going to learn multiple languages, I would still say that you should learn C#, Java, and MC++ before worrying about learning C# and VB. Knowing MC++ and C# can be a heck of a lot more useful than VB and C#, since there isn't really anything you can't do in VB that you couldn't do in C#. Java and C++ share pretty much all the same concepts / syntax as C# but can really come in handy when C# isn't an option (or you need to find a new job), and making the jump to either to/from C# is pretty easy.