Re: Thinking Clearly

Bob Dawson wrote:
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.

Yes, only if .NET code migration is important to you.

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?

It can be both, and some view it as such. I personally don't really
believe code migration is something that will entice a large number of
developers to pick up Delphi.

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?

What advantage does .NET provide over Win32 in this case? ISTM, both
are constrained to Windows right? End users aren't going to notice any
difference at all. If the development is the same, using the same
framework, i.e. VCL, there is no reason at all to use .NET.

IOW, the question is really why would you want to do both? IMO, the
reason to go .NET is to actually leverage what .NET has to offer. I
know, it sounds radical. ;)

In doing so, there will be dependencies on .NET itself. Hence IMO,
there's no point in writing a cross platform application if the two
platforms are Win32 and .NET. Which is why something like a mixed-mode
compiler is, IMO, a much better migration/integration strategy.

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.

Sure, and I believe that it is important for that reason.

My point is that it is important to view it beyond just that. It's
important to look at it in context of limited resources, importance to
the customer base (which remains largely Win32), opportunity costs, what
strategic advantage it provides and the competitive landscape of the
..NET development space.

--
Brian Moelk
Brain Endeavor LLC
bmoelk@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
.

Relevant Pages

  • Re: About speed
    ... But I mean - new platform must simplify ... available to .NET applications (and keep in mind coming libraries, ... writing a critical piece of architecture or a library that will be under ... .NET show BIG difference in architecture from Win32 so my ...
    (borland.public.delphi.non-technical)
  • Re: I have seen some fat client Dot Net apps
    ... business case from moving from Win32 to .NET with an existing code base? ... IMO, it's far more interesting to *add* .NET to Win32, ... and gradually introduce .NET to win32 developers without ...
    (borland.public.delphi.non-technical)
  • Re: MS dumbing down VC 2005?
    ... If you haven't done so already, install Visual C++ Express. ... Install the Platform SDK over the Web from the Download Center. ... One more step is needed to make the Win32 template work in Visual C++ ...
    (microsoft.public.vc.language)
  • Re: Documentation on dropped features in WinMo?
    ... CE) is a subset of Win32, ... that any given platform does. ... CE has clear documentation on what it does contain. ... owner draw combo boxes and list boxes (hmmmm... ...
    (microsoft.public.pocketpc.developer)
  • Re: I have seen some fat client Dot Net apps
    ... it does prevent me from taking advantage of the other platform. ... The biggest hurdle in porting existing Win32 -> .NET is third party ... and it's the same as the reason why many Delphi ... developers haven't embraced .NET. ...
    (borland.public.delphi.non-technical)