Re: The New Roadmap

Bruce McGee wrote:
What's better in Delphi for .NET than C# or Chrome?

Off the top of my head:

Language compatibility between .Net and Win32 and even versions of the
compiler.

C# and Chrome don't have these issues because they don't have Win32
versions.

The question is about .NET and it goes directly to the heart of Delphi's
..NET flawed strategy. IOW, is Delphi for .NET *significantly* better
than the defacto standard alternative?

The only way code compatibility comes into play is if you're a Delphi
Win32 user anyway. Which at that point:

The VCL:
- Is compatible between .Net and Win32.
- Comes with source.

(IMO, that is actually one thing that is better about VCL for .NET that
doesn't get talked about too much. It's a shame we can't say the same
thing about ECO.)

- Remains compatible between versions of the VCL, unlike Winforms.
- Paints noticeably faster than Winforms.
- Is continuing to be developed, unlike Winforms.

Might as well use Win 32 for the VCL. Opens up lots more third party
options.

Unmanaged exports.

Ok, one can simply use COM for interop from other .NET languages.

Virtual Library Interfaces.

Can you explain what you mean by this?

--
Brian Moelk
Brain Endeavor LLC
bmoelk@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
.

Relevant Pages

  • Re: Statement on backwards compatibility?
    ... MS made a very profound statement about WIN32 compatibility many moons ... No compile errors or warnings and I was able to run it all ... > refer to the expectation that products compiled on a higher O/S ...
    (microsoft.public.win32.programmer.kernel)
  • Re: The New Roadmap
    ... Language compatibility between .Net and Win32 and even versions of the ... Is compatible between .Net and Win32. ... Remains compatible between versions of the VCL, unlike Winforms. ...
    (borland.public.delphi.non-technical)
  • Re: Statement on backwards compatibility?
    ... You have just described a problem of upward compatibility ... >> this fundamental statement of WIN32 compatibility guarantee. ... No compile errors or warnings and I was able to run it all ...
    (microsoft.public.win32.programmer.kernel)
  • Delphi refocussing on .Net - good or bad?
    ... It's intersting to see an indication that they will be focusing more on cutting edge than compatibility. ... Personally I'm ) starting to think that .Net is not just a new "version" of Win32. ... So Delphi for .Net should probably be considered a completely separate product, like JBuilder or Delphi for PHP, rather than just a new version of Delphi for Win32. ... So, in that respect, compatibility is probably rather unimportant, compared with keeping up with the .Net versions and other emerging .Net technologies. ...
    (borland.public.delphi.non-technical)
  • Re: Catastrophic Failure Trying out VCL.NET
    ... of Delphi, even across different platforms. ... Not because I want whole projects to run in Win32 and .Net at the same ... The biggest value I see from this compatibility is the ability to have ... including Winforms. ...
    (borland.public.delphi.non-technical)
Loading