I find it interesting that MS is putting so much effort into .NET and yet all developers will have to learn new languages to use it, not just new libraries.|
C# isn't Java or C++, though it will be easy enough to pick up.
VB.NET has incompatibilities with existing VB 6 code.
It's not just ease-of-learning here, as the article points out it's also the ease of migrating existing stuff, getting it to work under .NET.
Sure .NET allows for any number of languages. But I don't that there's any reason to use Perl.NET or Python.NET (for example) unless I really, really need to interoperate with other objects written for .NET.
I can write Python (or Perl or whatever) code that integrates with a service via SOAP right now and not have to be using Python.NET.
I'd actually much rather be using C# to write objects for use in my web projects than using C++ to write COM objects... but what about all my existing COM components? We can't justify rewriting them just-because.
I'd also rather be writing my .ASP scripts in VB.NET instead of VBScript... but we can't migrate our stuff page-at-a-time whenever .NET is ready for prime time. It's an all-at-once rewrite of all of our tested code.