The new Windows 7 phone is living up to its hype. The little the I played with it - it proved to be just as snappy as an iPhone. You won’t see me trading in my Droid just yet but credit is due!
I was surprised at the XNA conference to find that XNA currently doesn’t support VB. It is important to point out that the XNA team is small, and support for VB is on their (someday) feature list. The fact that it was even optional by MS came to me as a surprise.
I recently landed a new job where they prefer VB. This has forced me to take a step back and analyze the difference between C# and VB. I started out with VBA and VB.NET but in my last job I fell in love with C#. I now find myself wondering if I have a good reason to like C# over VB or if it is just a comfort bubble. I am finding that there are far more reasons to go with C# than VB.
Less important (for me) is the transition to other platforms like C++ and Java. VB has the advantage of VBA and VisualFoxPro but VisualFoxPro is already in end of life and I believe VBA is (or already has) gone to .NET which will mean that you can use either language.
Another point worth mentioning is that a majority of the documentation on the internet, in books, at conferences is all C#. Check out PDC – how many videos are in VB?
At the end of the day – I believe that each language has its strengths – and being flexible to the language is a must. But those that say you should be completely language agnostic ignore the fact that by focusing and embracing on a language – you become a master with the language. The language becomes a tool and as such – an extension of your creative ability. Being (too) language agnostic will create an implementation barrier as you are unable to gain momentum. Your intelligence is shifted from business logic problems and onto syntactic problems.