I've had to pick up a couple of VB.Net projects. They've both been poorly written, badly implemented and years if not decades behind the time. There's a reason

I've had to pick up a couple of VB.Net projects. They've both been poorly written, badly implemented and years if not decades behind the time. There's a reason for the sneering. One of those I've virtually completely rewritten in C# and the code base is now like 30% of the TLOC. Not because of the language, but because of the type of programmer who started a new project in VB.Net in the last 5 years. For all intents and purposes the languages are virtually interchangeable, though C# is generally more succinct and somehow "better" to me. I don't even really think about it when switching between the two. UK projects, for reference, where .Net has always penetrated further than Java. I also still get an inordinate amount of calls because my linked in profile list VB.net asking to 'upgrade' a project from VB.Net to C#. Then again, the salesforce offers I get too... Ugh, much worse than VB.Net.