A friend of mine coined a word for that exact concept. He called it a prograsm.

VB.net is my primary language. I use it in an OO manner just as I would with C# but the stigma and lack of tooling (re: Mono) is getting to be a big problem. I'm looking around for a different job and I'm being careful to only talk about my experience on the .net framework rather than VB as a particular syntax because I've heard and seen people automatically dismiss VB without further thought. I'm productive in VB because I know and understand the syntax. While I can work in C#, I know that I'm going to have to climb the learning curve to get as efficient with the syntax as I am with VB. On the other hand, I need to do some things with my primary application in order to satisfy my customers and the tooling that I need to accomplish that and maintain compatibility is only available in the C# world. It's a shame that I have to change syntax as much because of reputation as tooling, but at least I'm still able to work in the framework so I can maintain that part of my knowledge and experience. I will say though that in my opinion... VB is no more verbose than C# in daily use and the 'shape' of functions is much clearer to my practiced eye than C# functions. I find that the commonly used style for C# eats up much more vertical space than a similar VB function and that horizontal space is very similar between the two.

SixOfTheClock wrote:

3. Those that have acquired an illogical, extreme hatred for it through an unholy combination of hearsay, rumour and code samples (often VB6) they've seen on the internet. They have never tried it and so are horribly uninformed on the topic. They say things like "VB isn't a real language!" and "VB is a language for babies!". It is with this group that I take issue.

This point gripes me to no end. I can't understand it from a logical perspective EXCEPT... that I've been in local college courses for both syntax's and found that the instructors treat the two languages in orthogonal manners. C# instructors teach OOP, while VB instructors teach quick and dirty almost linear techniques targeted more at Win-forms than at real-world apps. I have to wonder if this is systemic across the industry and helps to propogate the stigma against VB in the real world. This isn't to say that the local C# courses are very good mind you... when the advanced C# instructor taught ASP.net data access (one year ago) using techniques that were the definition of a SQL injection vulnerability and then didn't back down when