Well, okay, it's not all about him, but that was the part of this CodeProject article that I found the most compelling. I ran across this in a discussion over at Joel's. I'd like to credit "RandomPunter" for the link, but I'm not sure if that accomplishes much.

Recap: We all know that C# and VB.NET are effectively tied with each other, feature for feature. If you think late binding, implicit casts, and implicit event management are always a good thing, you tend to like VB. If you think that early binding to interfaces, explicit casts and explicit event management are always a good thing, you tend to like C#. So, how to choose, other than arbitrarily?

Here's a suggestion. Look at the culture. Who built them? Who uses them?

It's a nice idea. It'd be interesting to see the article developed further with some insight into the VB.NET culture as well as the VB6 and the C# one. I'm not sure I agree entirely with the article. I guess I never seem to agree with anything entirely. The comments have some good points, such as that allowing less skilled users to get work done is actually a good thing, a point for VB.NET. And certainly there are plenty of skilled VB6 users.

Trying to remain neutral, I think, somebody added this comment: Surround yourself with good people going in the same direction and everything will work out peachy. Good advice. Looks like the people whose work I'm following online all somehow seem to be using C#, Java, or C++, or occasionally good stuff comes from the Python/Ruby area - the new language crowd. No VB, somehow, except for Lhotka who keeps his work accessible to all. Well, that's one decision made.

Seriously, the article also has a good history lesson on recent development languages. It's from a C# bias of course, but since that's my bias I'm okay with that.