I really knew Delphi and C++ builder were dead (niche tools) when Anders Hejlsberg
left Borland for Microsoft. For those that don't know, he was the key guy
on Turbo Pascal and Delphi. After he arrived at Microsoft, he did some work
on Java. Then came the lawsuit with Sun and he sort of dissapeared. When
I first heard the rumors of COOL, I knew he had something to do with it.

Sure enough here comes .NET and it has his fingerprints all over it. VB
gets a full rework to fit in. VB.NET has objects that really work like objects;
VB.NET is a first-class citizen that can do everything any other .NET language
can do without annoying hacks; VB.NET even does threads; And, unfortunatly,
Microsoft had to change things quite a bit to make it all work properly.

VB.NET is more of a professional programming tool than VB ever was. It is
harder to get started but it will be easier to get substantial things done.
I'm not trying to say VB cannot be used for large systems. I've used it
for large systems. I am saying that it lacks many of the language features,
mostly OO, that make big systems easier to put together and maintain. When
you add in the elegance of the CLR and the much-improved web programming
model, I think you would be somewhat silly to pine for VB6. I agree with
McKinney when he says VB is dead and VB.NET is nothing more than C# with
VB-like syntax. However, I say that if you like VB you should go ahead and
use VB.NET.

Old code is important. Don't worry, the porting tools will get better.
After all, this is only beta 1.

The bigger question, I think, is whether or not .NET will live up to the
promise of cross-platform portability. If someone, maybe even Microsoft,
ports .NET to Linux, I think Java will be just another .NET language. If
not, I think .NET might be a flop.

I will wait and see. I will use VB.NET. I will use C#. I doubt I will
miss VB very much.