@nsnavare: I think the point I am laboring to make is this ... VB gets compiled down to the same IL as C# and other managed languages. In that regard, it is no different from C#. However, there's a different culture around C# than VB. This speaks to the quality of reference materials available. For example, look on the http://www.asp.net website ... there are no VB examples. On Microsoft Virtual Academy -- most topics are only covered in C#. At TechEd or Build conferences, I can't remember seeing a speaker use VB to demo a given feature. Most books only have source code examples for C# for a given topic. Most StackExchange answers are provided in C#. So, again, I'm not disparaging the language. It is sufficient to handle virtually any task that C# can handle because they use the same tools. The true difference is in the experience as a result of the Microsoft development community at large. Hope that makes sense.
Just to be clear, VB *is* different from C++ because you can create either managed or unmanaged C++ applications.
@stahtufiang: Thank you for the good thought. Let me explain my rationale. (1) Keep in mind, this series is for absolute beginners with no programming experience at all. In less than eight hours we go from 0 to LINQ ... that's a huge leap. The fact that generics is something you want to know makes me guess this isn't your first rodeo, so to speak. You have programming experience already, correct? (2) Microsoft has a budget on what they're willing to spend, so somethings can stay and some things have to go. (3) IMHO, generics is not a beginner level topic. In fact, IMHO generics goes to the bottom of the list behind more OOP topics like interfaces and dependency injection. I mean, you definitely need to know what to stick between the angle brackets (that's why I say "you make a generic specific by giving it a data type"), but beyond that I think you're ok with just understanding it at a surface level.
There are many series on Channel9 and MVA that can take you from here to that next level. Actually, my personal regret:I should have added something about async because you can't use WinRT or many of the new .NET API's without it.
Thank you again for your comment. If we ever do this series again, I'll be sure to give that some serious thought.
@Tony: I would say that you should not be discouraged when it comes to classes. Just accept the fact that they're used and how to create new instances of classes as created by Microsoft in the .NET Framework class library. Frankly, it took years before it really clicked for me (I'm slow). So, again, don't get discouraged. Just plug away a little every day and keep trying to consume explanations from different authors. Good luck!