Re: Thinking Clearly

"Brian Moelk" wrote

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

'Code migration' is a deceptive term, since migration generally implies
one-way. Cross-platform (win32/.NET) development will continue to be a
significant reality for some years.

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.

And I don't see that Delphi developers have anything special about them in
needing to live in multiple worlds. That's where your 'code-migration'
terminology is misleading. Win32./.NET cross-compatibility is not just about
legacy code. It's about supporting both platforms for some time to come.

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.

That doesn't follow at all. You can cook both haute cuisine and burgers on
the same stove. It's not like using VCL.NET prohibits exploiting the FCL for
all it's worth.

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. ;)

No, it sounds obvious. It just has nothing to do with whether one chooses a
Form or a TForm for the front end.

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.

Cross-platform evolution certainly makes sense for existing code bases. For
new work it might or might not. But I just don't see any reason why a
developer interested in learning TForm use in the win32 personality would
want to ignore that knowledge when writing another program destined only for
..NET existence. If the intention is to spend as much time on the problem
domain as possible, and as little on the tools as possible, then why use
different tools in every other program to whatever extent commonalities
exist?

Which is why something like a mixed-mode
compiler is, IMO, a much better migration/integration strategy.

FWIW, I'd strongly support a mixed mode compiler. I'm just not interested in
arguing that its the only thing DevCo should be working on.

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.

I believe that that's all in Nick's job description somewhere. And I'd bet
he's doing it as fast as he can.

bobD


.

Relevant Pages

  • Re: Thinking Clearly
    ... 'Code migration' is a deceptive term, ... I contend that "Cross-platform" is also deceptive. ... While you may have no need for cross platform *applications*, ...
    (borland.public.delphi.non-technical)
  • Re: Thinking Clearly
    ... 'Code migration' is a deceptive term, ... I contend that "Cross-platform" is also deceptive. ... difference between .NET and Win32. ... reason to go .NET is to actually leverage what .NET has to offer. ...
    (borland.public.delphi.non-technical)