Re: About speed

"Joanna Carter [TeamB]" wrote:

The point that you are missing in this discussion is that Delphi for .NET
is
trying to allow you to port your legacy code to .NET but, in so doing, it
is
lulling you into a false sense of security.

Somehow this important point gets glossed-over in most discussions of Delphi
for .NET!

Programming for a managed environment is not the same as programming for a
deterministic memory model.
<snip>
You really need to understand that, although you appear to be using the
same
compiler, you really are not. The target platform is not just Win32 with a
different library, the Delphi for .NET compiler targets a totally
different
memory model and runtime library.

Yep .NET sure ain't your Fathers Delphi! :-)

IMO, *good* Delphi for .NET projects cannot be simply recompiled from
Win32
source, there are many more considerations that will influence how a
progam
is written for a managed environment as opposed to an unmanaged one.

Yet there are way too many Delphi programmers that seem to believe that when
the time comes to migrate their apps to .NET hardly more than a recompile
will be necessary. It seems to me that too often Delphi developers decide to
test this hypothesis by recompiling a Win32 app. giving it a speed test and
shouting about the poor the performance and how they can't understand the
attraction of .NET and threads like this one is the result. IMO in the long
run this is not be helpful to the Delphi community.

What makes this thread so unusual is that several highly creditable people
like yourself have stepped forward to dispel the myth that .NET is slow and
inefficient. Hopefully someone will convert the contents of this thread into
a publicly available document that can be referred to in the future rather
than fighting the same battle over and over again.

...At least Delphi has
allowed you to program in a manner that prepares you for the totally OO
environment that is .NET. Even though you have to make small alterations
to
your code, most of the class and code structure will remain unaltered.

While at the same time Delphi lulls one into a mindset that the "Delphi way"
is the best way and regardless of the consequences they will try to force
..NET to bend to their way of doing things. The GC almost always gets
hammered.

Perhaps a book like Jon Shemitz's ".NET 2.0 for Delphi Programmers" should
be made required reading. ;-)


.

Relevant Pages

  • Delphi Community Many Times Stronger Than C++ Community
    ... because like most Delphi programmers I have a past history ... C++ community has a few strengths but in almost every area that really ... One guy will use MFC, another wxWidgets, ... Delphi programmers that I take for granted and just cannot believe their ...
    (borland.public.delphi.non-technical)
  • Re: God I Love Delphi7
    ... much better thanks and I do agree that Delphi programmers would ... developer tools. ... it compiles the pieces that it ...
    (borland.public.delphi.non-technical)
  • Re: Object Pascal Stigma, Useless Survey Question
    ... I understand that the technical feat to change it ... but all Delphi programmers will find it easy ... The problem is that have a well-defined meaning in Delphi - they ... I'm not sure how well your idea would fly if it was a pure syntax ...
    (borland.public.delphi.non-technical)
  • Re: Delphi book, C# book survey question
    ... but leave off the stupid part. ... somebody posted a question asking about a C# book for Delphi ... > barely a market for Delphi programmers wanting books. ... > more C# language books. ...
    (borland.public.delphi.non-technical)
  • Delphi book, C# book survey question
    ... somebody posted a question asking about a C# book for Delphi ... My .NET for Delphi programmers book has not sold very well, ... more C# language books. ...
    (borland.public.delphi.non-technical)