Re: vista avalon etc.

Chris Burrows wrote:



You said it - *with third party components*.

However, it's not just what you can do but how easily you can do it.
I rarely have to get into the debugger to track down elusive AVs for
example. Any exceptions automatically give you informative stack
traces without having to install 3rd-party add-ons.

Well, we know Microsoft wants to kill third party vendors. What I
meant was, if the VCL for Win32 is updated (It hasn't been in a few
years), there is no reason why it can't be better than .Net. As I
said, .Net is just another Win32 application.


You said it - *perhaps with a lot of code*. The less code I have to
write and debug the more easy my job becomes. The VCL was a brilliant
piece of work and using it was infinitely easier than writing
directly to Win32. Using .NET improves the process further, not as
dramatically perhaps, but still to a significant extent. An
additional 'enjoyment' factor which probably wouldn't apply to most
Delphi users is due to the ability for me to use Component Pascal as
my language of choice.

When I said, "with a lot of code", I meant with the VCL as it is now,
and then using more Win API to get at Vista or XP. I believe with an
update of the VCL, the advantage of .NET will evaporate. All the
language "improvements" of C#, VB.NET, etc., I think, don't make you do
less work, just maybe think about it a little differently. The
impression I get is that there are things you can program in C# that
you can't in Delphi (as it is now, without improvements), and we well
know that anything can be programmed in any language. Granted, some
languages might use less statements than others to get things done, but
sometimes that comes at a cost (less maintanability).

--

.

Relevant Pages

  • Re: Turbo questions
    ... I do share /some/ of the concerns about the artificiality of language ... innovation within the CLR context - for example, ... Language was never really Delphi's selling point anyway - the VCL is. ... the problem now that Delphi has /in the .NET space/ is that the ...
    (borland.public.delphi.non-technical)
  • Re: 64-bit Windows for AMD 64 is here...
    ... The choice of language is highly subjective, ... Delphi for .NET, OTOH, does not differ greatly from Delphi for Win32. ... they'll have to go WinForms because VS.net doesn't ... > know nothing about VCL. ...
    (borland.public.delphi.non-technical)
  • Re: 64-bit Windows for AMD 64 is here...
    ... Shares the same JIT, i.e. same runtime limitations and dependencies ... (and has more dependencies if you use VCL). ... Doesn't even have a complete help with exemples tailored to the language. ... > it should be easier to use it in the .NET environment than it was in ...
    (borland.public.delphi.non-technical)
  • Re: In My Dreams
    ... >> wipe out most of the Delphi third party market by bundling ... items are currently covered by third party products, ... an all-new VCL 2.0 rebuilt from the ground up to shed all the ...
    (borland.public.delphi.non-technical)
  • Re: borland vs. microsoft
    ... > in this language known as Object Pascal. ... I've never heard of Object Pascal except with Delphi ... > the more blatant mistakes is when defining AnsiString support in VCL ... I haven't used the free compiler much but I think it's cool that they were one ...
    (comp.lang.cpp)