DevSource has another article Will VB 9 Win Over the VB 6 Faithful? where the .NET advocates sing the praises of VB9 and the VB6 faithful bemoan how VB9 will be even worse for them than VB7 and VB8. Problem is, this entire issue has been clouded with emotion, like so many other issues as of late (For example can you say "Iraq War" or "Gay Marriage?" I thought you could.)
What I’d like to know is this: What are the real reasons why VB6ers feel they still need a new VB6 five+ years later? What tangible problems are they having that they can’t get solve by continuing to use the old VB6 for one set of problems and the new VB.NET for everything else?
BTW I’m not taking sides here; I honestly want to see if I can spawn a productive dialog per change to identify viable solutions Microsoft might consider implementing to make everybody happy. FWIW!
P.S. And please don’t say "I don’t want to/have time to learn it" because that’s just unrealistic in the technology industry. Welcome to the real world, after all.