Why Use Delphi.NET Over C#?
Frederick Chin
code samples, there were C# code.
What is the advantage of using Delphi For .NET over pure C# for
developing a web application quickly? If I were to use Delphi For
.NET, I would still have to learn C#. Why not just use C# in Visual
Studio?
Thanks for your thoughts.
Regards,
Frederick
VT Venkatesh
For e.g I already have Rad Studio Architect & using ECO with asp.net
with lot of success.Though I am also learning C# (so that i could
convert C# examples to Delphi)
Hence i am having best of both worlds
More over I certainly find vcl.net better than winforms.I have even seen
reports that that one can also do wpf in delphi.net 2007
Venkatesh
Frederick Chin
>It ll depends on one' knowledge of Delphi & investment in new tool.
>For e.g I already have Rad Studio Architect & using ECO with asp.net
>with lot of success.Though I am also learning C# (so that i could
>convert C# examples to Delphi)
How have you found Delphi.NET in Rad Studio as a tool for writing web
applications compared with other languages in terms of features and
ease-of-use? Let's say you have a web application project for an order
entry and delivery tracking system that must be delivered in 2 months.
Would you say that a developer who is familiar with Delphi VCL but
without knowledge of Delphi.NET be capable of delivering the completed
product in that kind of timeframe?
Regards,
Frederick
Wayne Niddery (TeamB)
news:drt6u3t2sgha7tg2u...@4ax.com...
>
> Let's say you have a web application project for an order
> entry and delivery tracking system that must be delivered in 2 months.
> Would you say that a developer who is familiar with Delphi VCL but
> without knowledge of Delphi.NET be capable of delivering the completed
> product in that kind of timeframe?
They will be *at least as capable* of doing so as anyone working in C# who
has an equal knowledge (or lack thereof) of the .Net framework, yes. Why
would you think a Delphi developer would be at a disadvantage?
In fact, because the .Net framework builds on so many ideas - and even
directly on many classes - that Delphi developers have been familiar with
for about 13 years now, for many the learning curve in .Net is *shorter*
than those having only worked with either C++ or VB in the past.
--
Wayne Niddery - TeamB (www.teamb.com)
Winwright, Inc. (www.winwright.ca)
Wayne Niddery (TeamB)
>I was reading Delphi For .NET Developer's Guide recently and in the
> code samples, there were C# code.
>
> What is the advantage of using Delphi For .NET over pure C# for
> developing a web application quickly? If I were to use Delphi For
> .NET, I would still have to learn C#. Why not just use C# in Visual
> Studio?
What has ever been the advantage of using Delphi/Pascal over C/C++ (or any
other language)? All the Windows API examples have always been in C/C++ (or
VB).
The same answers still apply.
Developing a web application requires learning about how web apps work and
coding according, whether you use WebBroker or you use ASP.Net. None of that
changes, but you are already familiar with built-in Delphi functions,
syntax, and capabilities so it still provides you an advantage.
That's not to say you *shouldn't* learn C#, only that you don't need to for
actual coding if you don't want to. But I will also say here that C# is
quite readable and I don't really understand why it's considered such a
burden for a developer working in Delphi to read code examples in C#.
If you *like* coding in Delphi, then code in Delphi.
Frederick Chin
>What has ever been the advantage of using Delphi/Pascal over C/C++ (or any
>other language)? All the Windows API examples have always been in C/C++ (or
>VB).
Speed of compilation, intuitive language, single executable, easy
deployment and more.
<snip>
>If you *like* coding in Delphi, then code in Delphi.
And that is what I want to do but using the Delphi .NET guide as a
reference, I noted that C# code was interspersed with Delphi.NET code.
Using Delphi VCL, I never had to bother with ASM or C code to be
productive but this .NET development environment seems to require
using C# code at times.
I was wondering that if this is the case, why not just go straight to
picking up C# and be done with rather than to learn both Delphi.NET
and C#.
Like you said and I concur, C# is quite easy to read.
Regards,
Frederick
John Moshakis
>
> And that is what I want to do but using the Delphi .NET guide as a
> reference, I noted that C# code was interspersed with Delphi.NET code.
> Using Delphi VCL, I never had to bother with ASM or C code to be
> productive but this .NET development environment seems to require
> using C# code at times.
>
> I was wondering that if this is the case, why not just go straight to
> picking up C# and be done with rather than to learn both Delphi.NET
> and C#.
>
Hi Frederick,
I find that most of my time is spent learning the dotnet framework. You
can implement applications using the libaries in the framework in which
ever one you prefer.
Cheers,
John
--
danny heijl
> I find that most of my time is spent learning the dotnet framework. You
> can implement applications using the libaries in the framework in which
> ever one you prefer.
While this is true, one should also consider the fact that win32 Delphi
code recompiled for .Net can be literally thousands of times slower than
equivalent (properly written) C# code.
If you rewrite the Delphi win32 code for Delphi .Net (avoiding the
Borland System unit and replacing old Delphi constructs with new ones
like New instead of SetLength and the appropriate framework classes like
StringBuilder instead of string concatenation or direct string
modification and so on) performance should be close to C#.
So the question is: why bother with Delphi for .Net if you have to
rewrite it anyway?
Danny
---
VT Venkatesh
> How have you found Delphi.NET in Rad Studio as a tool for writing web
> applications compared with other languages in terms of features and
> ease-of-use? Let's say you have a web application project for an order
> entry and delivery tracking system that must be delivered in 2 months.
> Would you say that a developer who is familiar with Delphi VCL but
> without knowledge of Delphi.NET be capable of delivering the completed
> product in that kind of timeframe?
>
> Regards,
> Frederick
Actually I found delphi asp.net with ECO very easy to use compared to VS
with ECO since ECO is not integrated with VS compared to RS.
How ever whether one uses C# or delphi one has to know asp.net.Once you
know that I find Delphi easier since i am using Delphi for a long time
Venkatesh
Frederick Chin
>Actually I found delphi asp.net with ECO very easy to use compared to VS
>with ECO since ECO is not integrated with VS compared to RS.
>How ever whether one uses C# or delphi one has to know asp.net.Once you
>know that I find Delphi easier since i am using Delphi for a long time
If I understand it, ECO is not included with Delphi Professional
versions. If I do not have ECO, will it still be productive with
Delphi .NET?
Regards,
Frederick
Frederick Chin
>I find that most of my time is spent learning the dotnet framework. You
>can implement applications using the libaries in the framework in which
>ever one you prefer.
Thanks for all your thoughts! I am going to create a simple contact
management application using both Delphi Rad Studio 2007 trial and C#
2008 Express Edition and see how it turns out.
Regards,
Frederick
Dave Nottage [TeamB]
> If you rewrite the Delphi win32 code for Delphi .Net (avoiding the
> Borland System unit and replacing old Delphi constructs with new ones
> like New instead of SetLength and the appropriate framework classes
> like StringBuilder instead of string concatenation or direct string
> modification and so on) performance should be close to C#.
In what circumstances do using those routines result in a significant
performance improvement?
--
Dave Nottage [TeamB]
danny heijl
> In what circumstances do using those routines result in a significant
> performance improvement?
String concatenation and string modification result in huge amounts of
memory reallocations (a new string is allocated every time and the whole
string is copied over).
SetLength for array initialization is very inefficient in .net, and you
should use it only for array reallocation.
I have extremely bad experiences with the .Net port of the EKRTF package
due to this kind of issues.
The win32 version flies, the Delphi .Net version is (literally) 1000's
of times slower due to the heavy use of that kind of constructs.
Just try the following and measure the performance in both environments:
var
s: string;
i: integer;
begin
SetLength(s, 1000);
for i := 1 to Length(s) do
s[i] := 'x';
end;
It will help if you can read IL (using Reflector for instance) to
explain the performance hit.
Then try the following equivalent in Delphi .Net:
var
s: string;
sb: StringBuilder;
i: integer;
begin
sb := StringBuilder.Create(1000);
for i := 1 to 1000 do
sb.Append('x');
s := sb.ToString();
end;
This should be very close to the equivalent C# code performance, because
it is written "the .Net way".
Danny
---
Frederick Chin
><Warning: rant>
>You won't miss ECO. It was a part of the 2006 pro SKU and it was an
>instable, undocumented horror.
<snip>
In this case, it won't be missed.
<snip>
>Beyond that the webserver and your web application are totally
>oblivious about what happened before.
>You're the one that needs to implement the "remembering what went on
>previously" logic.
Based on your opinions, why would you continue to use ASP.NET as
opposed to PHP?
Regards,
Frederick
VT Venkatesh
>
> <Warning: rant>
> You won't miss ECO. It was a part of the 2006 pro SKU and it was an
> instable, undocumented horror.
> and in German. I wasn't able to do even a single example because it was
> geared at an even older version that had different names for things.
> </Warning: rant>
>
> Besides that, working with ASP.NET & Delphi is a breeze.
The older version of ECO was exactly as you had put it.
How ever with Dot Net 2 & ECO IV things have changed dramatically &
today I do all my asp.net with ECO.
Documentation has improved though i won't still call it as adequate
It is a potent combination & worth giving it a try.
I am really glad I had bought Delphi architect.It is worth the money
Venkatesh
Benedictum
I just found out from the web sometime back. I just could not place where I
saw it.
I develop apps on both RAD2006 and VS2008. I am more at home with Delphi - I
worked with it ever since the ancient $30 Turbo Pascal. Only reason I had to
learn C# because of my fear that Delphi users are dwindling and eventually
could lead to its demise. In C# I miss the VCLs though.
For .NET VS2008 has the advantage hands down! Delphi rocks with VCL apps! I
love them both!!
"Frederick Chin" <fchintc_...@ctsoftware.com.my> wrote in message
news:daheu3hdlrve2r0d7...@4ax.com...