Re: Captain Jake's Top Ten List of what I'd like to see in thenextversionof Delphi

Dennis Landi wrote:

That's disingenious since the proposition isn't moving from MFC apps
to .NET but from Delphi Apps to .NET.

I took the argument to an extreme, admittedly. My point is that like
or not, .net is a new platform and we're going to see more and more
stuff from Microsoft that pushes us into that world. I don't believe
we should be stuck with WinForms as a rich client framework, anymore
than I think we should be stuck with MFC, ATL, or any other single
framework for writing apps. VCL has been enormously productive -- I
don't want to lose that, Windows or .NET or whatever.

As has been discussed here before ad infinitum. Its a product in
search of a market (in delphi community). Instead, I'd rather see
DevCo focus on what the customers are asking for instead of trying to
devise ways to move away from a platform they don't want to leave...

The market is there - unfortunately, the market has not been well
served, in my opinion, by Borland. Numerous talks I've had with
companies who are 'exiting Delphi' indicate that many of them are
blissfully unaware that their code will port to .net if they insist on
a platform change.

Use of "Interop" here is fuzzy. IMO, the average Delphi developer
sees no need to leave natively compiled Delphi to do .NET WinForms
development.

I wonder who the "average Delphi developer" really is. Who is he?

So, IMO, VCL.NET is sucking resources away from more vital areas
that
would positively impact the existing customer base, better;
or,attract new users from other toolsets (such as ECO).

Legacy code isn't going to poof...and leverage is leverage and there's
a LOT of leverage in well written VCL components. Throwing an
investment in the trash can is not the way to move forwards in my
opinion, and if VCL can do .NET great, then that's leverage I'm
interested in.


I would hate to see ECO continue that exact same failed strategies
implemented by Borland

Well, we agree on this.

But here is the real promise I see in ECO: It is, perhaps, the
next
RAD platform. It
wraps .NET at the moment. But as an MDA artifact; it could
conceivably "wrap" any concievable platform. This is exciting;
and if it works well enough and offers the correct points of
interface to professional software engineers who have their own
code and agendas, it could well be a killer platform...

I think we both agree on the huge upside potential for ECO.

I could care less about WinForms and I sure don't need to waste time
figuring out how to compete against a technology that is irrellevant.

What other rich client development can you do in .net?

Randy



--

.

Relevant Pages

  • Re: C#Builder 2007(2008)
    ... ..Net is a platform that we leverage to the advantage of Delphi ... Delphi developers to leverage ASP.NET to develop web sites. ...
    (borland.public.delphi.non-technical)
  • Re: Whats the big deal with cross-platform?
    ... platform, or should be able to produce the executable that someone requires on their desired platform, but I always wonder why? ... I would like to be able to write apps in Delphi that work on all flavours of Windows, all flavours of Mac OS, and all flavours of Linux, but I reckon that I would spend more time working on compatiblity than functionality, so the end result would be compatible but non-functional. ... Delphi is good at both of those, and can remain good at both of them without even considering cross-platform hi- ...
    (borland.public.delphi.non-technical)
  • Re: Borlands linux strategy ?
    ... Sorry, it's the general mentality of Borland, and reinforced by users who ... believe that Delphi should just remain a windows platform tool. ...
    (borland.public.delphi.non-technical)
  • Re: The alternative Delphi roadmap to success
    ... what was the planned USP of Delphi, ... Market research is only a foundation: you need a clear vision to build ... this with the problems of shoehorning a language into a new platform, ... but with enough complete responses will REALLY help DevCo. ...
    (borland.public.delphi.non-technical)
  • Re: Delphi for IPHONE
    ... better learn something new because Delphi is not there. ... then I will not be writing for the iPhone and Mac market. ... Windows platform, has spoiled us and made us lazy to adopt new technologies not supported by it. ...
    (borland.public.delphi.non-technical)