The language wars are heating up again. Carl responds to a link to this page: Reasons To Convert From VB.Net To C#. The comments on Carl's blog were fast and furious but I can't really understand the crap that some of the C# people pile upon VB developers.
Rory picked up on the thread as well, adding his two cents in his usual humorous way.
My point of view falls in line with these two guys; Use the best tool for the job and for your situation!
If you're a C++ developer, it's natural to gravitate towards C#. If you're a VB guy stick with what you know and use VB.NET. Unless you REALLY need to do something specific that one of the two languages support, or if the shop you're working for requires a specific language, there's not much difference between the two.
Anyways, this list of reasons is just a list for some developer to use to try and convince their managers (who probably don't know any better) that C# is better than VB.NET. Kind of a coincidence that they happen to sell a tool to convert VB 6 code to C# right? No hidden agenda there...