Not Another C# Versus VB Article

Even if the author entitles the article as “Not Another C# Versus VB Article”, it is exactly what he is doing. The article, comparing to the other ones I read so far is a good one and documented well. It is also an aggressive one, kind of negative attitude against the VB.
I agree with most of this article, but the author forgets one very important element, probable the most important element considering software development: It is not about the TOOL to be used, it is always about the expected results and final product. Depending on expectations and project limitations a tool is to be selected to reach to best results in given time and with the given resources. Focusing on the tool instead of focusing on the result might lead you to failure in delivery but to a great understanding and usage of the tool. What do you chose?

http://www.codeproject.com/useritems/CSharpVersusVB.asp