You are worried about moving off of delphi?  Borland still supports Delphi,
and it is a fast platform, but it doesn't have much marketshare and Borland
has been pushing their Java products much more for a very long time.  I can
see a good reason to move off of Delphi.  It just isn't the main focus of
its vendor.

.Net is the main focus of Microsoft platform tools.

.Net 2.0 is fairly fast.  That said, any language that requires a two-step
compile can suffer some performance hits.  Java has the same concerns.
Between Java and .Net, you have probably 80% of new software development, so
I think we are safe to say that the idea has legs.  :-)

LOL!  .Net was rolling out generic support before Java was.  It is a fully
mature, fully vetted, wildly popular, extraordinarily stable platform.
Waiting will give you grey hair... not much else.

Did you say you were still using Delphi?

That depends on your app.  Some users will experience some loss in
performance if you make a one-to-one conversion of the app.  The techniques
needed to optimize .Net are different than the ones used to optimize Delphi
or C++, so apps that are ported often have some initial hiccups because the
'tricks' used to speed up Win32 apps can slow down a .Net app, and because
the dev team familiar with Win32 apps isn't familiar with how to optimize
for .Net.

Fortunately, this can be solved for the price of an ebook.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag/html/Scal
eNet.asp