The Visual Basic Team talks about the VB & SilverLight.
From the blog post: [emphasis added]
Prior to the announcement of Silverlight 1.1, Silverlight plug-ins were written in XAML and Javascript. While the Javascript model is certainly powerful, using VB is always my preference—it’s a language I know well, and its flexibility suits my programming style. Not to mention that the introduction of VB.NET into the Silverlight world brings with it many of the .NET Framework’s types and APIs I’ve come to rely on.
Given that most folks out there doing Flash and Web 2.0 work already use ActionScript and JavaScript respectively, adding a new language to the mix doesn't seem like a good move.
Unless of course, you add extra functionality to make it more palatable. Now will the non-developer set get the message that access to .NET Framework types and APIs will benefit them?
[found via Paul Vick]