According to Robert Hurlbut's blog Don Box has said that VB.NET will support generics. Now I thinks this is great. Coming from a typical VB background (started with VB2 in the early nineties), it's great to see a language evolve to become as mature as C++. Alright, this may be a bit too long a stretch, but generics does seem like a great feature. I doubt whether most vb-developers will use it, and that's the basic problem I guess between VB vs. all other languages.

VB is very popular, but mainly because it's relatively easy to learn. Especially VBA, which most people learn by recording a macro and then manipulate the code.  This, of course, has little to do with programming, but a lot of people seem to think they are developers just by manipulating recorded code and maybe copying someone else's code to perform a specific function. So many times, I've been asked to look at some code, be it VB or VBA, that didn't work properly. Just looking at what they were trying to accomplish made my stomach hurt. How do you deal with that? Do you suggest a solution or did try to convince them to give up this exercise and get back to what they were hired to do? I work with financial people mainly.

Back to generics. I'm grateful that this will be available. Switching back and forth between C# and VB.NET (C# at home, VB.NET at work) will be easier.