Your three options seem a little narrow and biased, exactly what you are accusing those who do not like VB.Net of being. :) For me personally I do not like VB.Net as a language. It it far too verbose and has way too many keywords. For a number of years it lagged behind C# on supporting new features of .Net. And Microsoft should have never created the Visual Basic 6.0 Compatibility library. I prefer languages that have a statement terminator that is not a new line and just gravitated to C# because I come from a C-based background and enjoy its terseness. Warning, I am using a broad stroke to generalize below and know that there are good and crappy programmers regardless of the language. My biggest grip with VB.Net however is the type of developer that it tends to attract, that being people from pre-.Net VB. VB was never a very good language and didn't have good OO support. Putting a blob of procedural code in a Class file in VB6 seemed to be as object oriented as most pre.Net VB developers went. I have been developing professionally for 15 years now and while I have met very good developers that like and use VB.Net, most do not fall in to this category. Instead they are the type of developer that has an extremely limited knowledge base. Asking them to move outside of VB and SQL Server is as if you asked them to perform open heart surgery. Trying to get them to grok Oracle, MySQL, SQLite, Linux, Java, Python or non-MS-Only standards was always a hair-pulling exercise in frustration. Back in the days of old ASP these were the type of developers that I had to go and rip out their VBScript or IE6-only JavaScript and replace it with something cross browser. In meetings for new development where we could chose technology they were the type to push only for VB and SQL Server, not because they were the best solution but because that is all they knew. The majority (again, not all) of VB.Net developers I have seen over the last 3 years or so haven't even put in the effort to learn the greatness and fullness of the .Net library, instead opting to use the Visual Basic 6.0 Compatibility library to hold their hand. To me it seems languages such as VB and Cobol tend to attract someone who is more of a business person over a developer. The type of person who isn't as passionate about the technology and more about just getting a job done (there is nothing wrong with that). I am just the polar opposite; I am very passionate about the technology and always want to stay current (it provides for my fami