Re: Thinking Clearly

"Brian Moelk" wrote
benefits to VCL.NET. So I'd like to take a step back and ask
honestly: What are the other benefits in choosing VCL.NET over
Winforms?

Cross compatibility for /continuing/ to write win32 apps with the same basic
language and library. VCL/VCL.NET isn't only about legacy code: Win32 code
continues to be written as a platform of choice.

If the primary value is code migration, then it's fine to just say that
VCL.NET is more of a customer retention technology rather than
one that will bring new developers into the fold.

Why does it have to be one or the other?

Certainly there are some that will appreciate the two-way code
migration capabilities of Delphi for .NET and VCL.NET and that
might bring a few guys on board. But FMPOV, that looks like a
very narrow segment.

Depends on who those prospective 'new guys' are. If you assume they're only
interested in Delphi for writing win32 _or_ .NET programs, then maybe the
combination of VCL/VCL.NET might not be very attractive. But why make that
assumption? Why would only existing customers have continuing interest in
writing for both win32 and .NET with a single approach?

In any case I'm not sure what your point is. Even if your claim were granted
that VCL.NET can only matter as a retention technology, it would still be
important enough on that basis alone to be a mandatory continuing feature
for quite some time.

bobD


.

Relevant Pages

  • Re: 64-bit Windows for AMD 64 is here...
    ... Of course the VCL for NET is ... classes (or structs in Win32) around. ... although not as extreme as the Win32 API. ... Delphi is also very strong on native compilation. ...
    (borland.public.delphi.non-technical)
  • Re: Delphi 2005 Win32 development stopped
    ... improve Win32 development or make a significantly better product for the end-user. ... Delphi, they wouldn't even merit a foot-note in marketting. ... someone from Borland or TeamB mentions for-in loops. ... and inherit all the bugs. ...
    (borland.public.delphi.non-technical)
  • Re: Thinking Clearly
    ... a case where MS is sticking it to DevCo. ... The question I have is if it will support ... interop and the core win32 API are bedrock. ... Was Win32 "bedrock" when Delphi 2 was released? ...
    (borland.public.delphi.non-technical)
  • Re: Comparison about Win32 / DotNet / CSharp on Delphi, and a wish ...
    ... jobopenings vs the number of pure Win32 jobopenings. ... I don't care Delphi team develop .NET or C# stuff, but as a lot of Win32 ... delphi users, I've been so frustrated to see all the negative impact it ...
    (borland.public.delphi.non-technical)
  • need clarification
    ... Delphi is heading towards a .NET state. ... I *feel* the Win32 inclusion was to string the regular Win32 ... Since porting .NET code would be ... would .NET developers give up ...
    (borland.public.delphi.non-technical)