Re: Thinking Clearly

lurkio wrote:


I agree about the grouping you mention but the folk that I was
referring to includes (semi-) former Delphi folk who have caught
.NET fever in a big way and seem to want Delphi to follow suit
even whilst they themselves /are not actually using Delphi for .NET/
as it either isn't functionally complete enough for them due to
the feature lag or the fact that they view VCL.NET with distaste as
(to them) it merely encourages the transposition of old Win32 idioms
into the new .NET context. The irony for me is that Delphi support for
.NET (or, indeed, any other third-party vendor support for it) will
/never/ be cutting edge enough for them...MS absolutely hold all the
cards in that context.


What new 'idiom' do you get with .net? I can see maybe saying that
about a transition from ATL or MFC programming to .NET, but as has been
pointed out many a time, the Delphi approach to coding and the .NET
approach to coding have more similarities than differences.

I'd be very interested to see a Delphi poll where Delphi developers who
are using VS.NET are asked to rank the following rationales for this
decision (not saying each is true, but they can be the reasons that
someone might give)

- Everyone else is doing it, hence C# developers will be in higher
demand and thus more jobs.
- VS.NET development is more 'cutting edge' / 'cool' than Delphi
- VS.NET makes you more productive than Delphi
- Management has dictated that all new code be written in C# and
VS.NET
- Other

Referring to WinForms muddies the waters a bit as I was really
meaning going with "pure" .NET as opposed to VCL.NET but I agree
with the idea of going with a more pragmatic approach as opposed
to a religious one. Unfortunately, VCL.NET doesn't quite offer me
the pragmatic approach I would have liked.

I'm your polar opposite on this one. I find the "rewrite it all in
WinForms" approach to be religious and non-pragmatic, whereas "keep
using debugged and tested code that works" as more pragmatic. There
may be other ways to describe re-writing vs. migrating, but pragmatic
to me is when you leverage what you have, not toss it into the garbage
can and start over so that you can use the latest, 'sexiest'
language/tool that's out.

Randy
.

Relevant Pages

  • Re: Turbo Delphi Purchase Questions
    ... my code in Delphi which works well for QR, ... Pascal script suggests that you have to do that rather than coding it ... Our software contains reports which are compiled in, ...
    (borland.public.delphi.non-technical)
  • Re: I have seen some fat client Dot Net apps
    ... RAD, like in Delphi, is also just an advantage for the software ... developer. ... And yet coding for a GUI would take much longer and be more ...
    (borland.public.delphi.non-technical)
  • Re: Thinking Clearly
    ... about a transition from ATL or MFC programming to .NET, ... approach to coding have more similarities than differences. ... therefore not using VCL.NET as an ongoing new development platform. ... VS.NET makes you more productive than Delphi ...
    (borland.public.delphi.non-technical)
  • Re: Component Rankings, Startup Advice and other random tidbits
    ... To those of you that started an ISV: ... Did you do all the coding yourself on your first project? ... considering starting a new commercial software startup... ... I like the speed of app development in Delphi. ...
    (borland.public.delphi.non-technical)
  • Re: Moving from Delphi to C++
    ... I felt a need to reply to this message as it was virtually the only one written in a civil tone. ... We however are coding certain pieces which make sense in Java. ... >Delphi, ... >opinion of the way Borland is treating Delphi developers, ...
    (borland.public.delphi.non-technical)