Re: What I Think Delphi Needs to Do to Survive
- From: "Randy Magruder" <rmagruder@xxxxxxxxxxxx>
- Date: 10 Mar 2006 19:04:56 -0700
The choice of language is significant
Compared to library and platform knowledge, no it isn't.
if the programmer is knowledgable enough to use the fullcapabilities of a particular
language, rather than just the subset similar to other languages hehas had experience with.
The language reflecs the platform. For instance, if I am using Delphi
code and I have this in a loop:
myLongString := myLongString + anotherChar;
And I do this in a loop (such as scanning a file), performance is going
to be dog slow. Not because of the language, but because in Win32 the
compiler is going to be doing a ton of memory allocations for that
ever-expanding string. The knowledge there comes from knowing how the
compiler is going to interpret the language. However, that assumption
may or may not be true for IL...because unless you know .NET CLR you
don't know how it manages strings. So how important is the syntax?
The flaw is going to be there whether you write it:
myLongString = myLongString + anotherChar
or myLongString := myLongString + anotherChar
or myLongString = myLongString & anotherChar
When you are just generating basically the same IL against a JITter,
the language differences have far less meaning. Yes, there is a
'familiarity' with the idioms of a language to take into account, but
this is trivial compared to the ever-growing sizes of libraries.
There's more learning to be done just picking up the workings of a
single grid component nowadays than there is in switching language
syntaxes.
The use of .NET makes the proper choice of a suitable language more
possible as it is more language-agnostic than other platforms (Win32,
say). In the past, the platform or framework was a much more
significant limiting factor in your choice.
That might be true if you're talking about coding LISP or Python, but
VB, C# and Pascal are so similar in structure and idiom where it comes
to procedural coding that it makes no real difference.
While Delphi is not available for .NET 2.0 then, by definition, itcannot be a language of choice for that framework, whereas Chrome can.
And you gain basically nothing by using Chrome. May as well save
yourself the trouble and just use C#.
Randy
.
- Follow-Ups:
- Re: What I Think Delphi Needs to Do to Survive
- From: Jim Cooper
- Re: What I Think Delphi Needs to Do to Survive
- From: Andre Kaufmann
- Re: What I Think Delphi Needs to Do to Survive
- From: Chris Burrows
- Re: What I Think Delphi Needs to Do to Survive
- References:
- What I Think Delphi Needs to Do to Survive
- From: Captain Jake
- Re: What I Think Delphi Needs to Do to Survive
- From: Mike Vance
- Re: What I Think Delphi Needs to Do to Survive
- From: John Jacobson
- Re: What I Think Delphi Needs to Do to Survive
- From: Randy Magruder
- Re: What I Think Delphi Needs to Do to Survive
- From: Captain Jake
- Re: What I Think Delphi Needs to Do to Survive
- From: Randy Magruder
- Re: What I Think Delphi Needs to Do to Survive
- From: Lauchlan M
- Re: What I Think Delphi Needs to Do to Survive
- From: Randy Magruder
- Re: What I Think Delphi Needs to Do to Survive
- From: Chris Burrows
- What I Think Delphi Needs to Do to Survive
- Prev by Date: Re: Open Delphi?
- Next by Date: Re: Delphi for Obsolete.NET
- Previous by thread: Re: What I Think Delphi Needs to Do to Survive
- Next by thread: Re: What I Think Delphi Needs to Do to Survive
- Index(es):
Relevant Pages
|