Re: If MS had owned Delphi for many years now...

"Troy Wolbrink" <troy.wolbrink@xxxxxxxx> wrote in message
news:43f60bb3@xxxxxxxxxxxxxxxxxxxxxxxxx
1. Unicode support in VCL for Win32 would have been a reality many years
ago - it's been a standard across MS apps/tools for many years now. MS
seems to "get" world-ready software and its huge benefits.

2. Resources would not have been wasted on Kylix, taken away from
improving Delphi for Win32. VCL would have wrapped even more Win32 native
features.

3. A VCL.NET that provides a fairly thin layer over WinForms (and in
future a thin layer over WPF .NET controls). It's there to provide
source/feature compatability, but VCL.NET could use WinForm under the
hood. VCL controls could be used in WinForms.

4. "foreach..in" might have been used instead of "for..in" syntax since
this is what is used in the other MS languages.

5. While Delphi still had a native code version, there would be
a lot fewer native components and we would have be caught
in DLL Hell just like VB programmers.

6. The code generated would be a great deal slower so
as not to compete with MS C++.

7. Delphi would now be .NET only, the last native code version
being abandoned 5 years ago.

8. We would be stuck with the crappy MS form designer.

--
Charles Appel
http://charlesappel.home.mindspring.com/
Home of Chuck's Poker Libraries for Delphi,
Chuck's Video Poker and Chuck's Toys


.

Relevant Pages

  • Re: suggestion #2 for improving VCL.NET usage
    ... > is the lack of third party components. ... Personally, I avoid WinForms. ... my first choice is Delphi Native Code. ... Home of Chuck's Poker Libraries for Delphi, ...
    (borland.public.delphi.non-technical)
  • Re: Delphi C++ C#
    ... > stay with Delphi and go with Delphi 2005 or not. ... And the forms designer in 32-Bit Native Code ... Delphi is miles ahead of the WinForms designer. ... Home of Chuck's Poker Libraries for Delphi, ...
    (comp.lang.pascal.delphi.misc)
  • Re: Captain Jakes Top Ten List of what Id like to see in thenextversionofDelphi
    ... MFC and WinForms do not. ... For the Delphi developer, there is less of an argument. ... How many VCL Win32 customers have been asking their vendors to support ... Delphi developers, moving their existing Win32 application to .NET ...
    (borland.public.delphi.non-technical)
  • Re: need clarification
    ... > As it goes right now, Delphi is heading towards a .NET state. ... using Win32 Delphi aren't necessarily interested in Win32, but Native code. ... Innovation will continue outside of .NET. ...
    (borland.public.delphi.non-technical)
  • Re: The New Roadmap
    ... WinForms is not my first choice for .Net UI apps. ... for the VCL since Delphi 1. ... VCL in both places where it makes sense. ... Why would you ever *need* to write a .NET GUI app? ...
    (borland.public.delphi.non-technical)