17Mar/101
Dissing Visual Basic
Haha, check out the below snippet from a local employment listing. The company is looking for Senior .NET developers with C#, Visual Studio, JavaScript, SQL, Reporting Services, etc. and has the balls to call out that "Experience with Visual Basic doesn't count." WTF!
There is an ongoing debate between the C# & VB camps over everything and anything, but we all know both .NET languages compile into MSIL and then JIT'd to O/S specific machine code. Aside from some language differences, it is all the same shit!
It is apparent the employer does not know what the fuck they are talking about. Oh, here is another nugget to consider. Some of us know the employer! Lame. Lastly, I know VB guys who can kick their entire team's ass. Bets anyone?
March 18th, 2010 - 23:21
Wow! I had the recent opportunity to work with someone much smarter than myself. I realize there’s a stigma in the community against VB. So when he asked me what language I was most comfortable with, I knew VB wouldn’t go over well. Fortunately, he said “It doesn’t really matter it’s all the same MSIL. I’m sure your fluent in both.” And yes…I am. It might just take me a little ramp up time particularly in the LINQ department to get familiar with the syntax. The problem solving methodologies are there.
Nice post. One of the reason I consider you among the best. Problems can be solved in many ways. In fact in C# 4.0, the dev team is loosening some of their standards so that you can perform late binding because *gasp* VB can perform late binding where C# can’t. And yes, while being generally frowned upon sometimes there is a need.