Re: Replacement for delphi

Rudy Velthuis [TeamB] wrote:

Hmmm... what about Delphi for .NET? No need to learn the language, no
need to learn WinForms, and porting should be a lot easier as well.

It does sound like quite a drastic move. Perhaps he should start
building his new stuff in C# first and then see how it goes from there.

--
Dean
.

Relevant Pages

  • Re: Replacement for delphi
    ... Dean Hill wrote: ... no need to learn WinForms, and porting should be a lot easier as ... It does sound like quite a drastic move. ...
    (borland.public.delphi.non-technical)
  • Re: VCL.NET the way to go
    ... Rudy Velthuis [TeamB] wrote: ... It can hardly be called RAD. ... The VCL.NET is a lot more mature than WinForms ... I would also prefer the VCL over WinForms for new ...
    (borland.public.delphi.non-technical)
  • Re: Is VCL dying yet?
    ... Rudy Velthuis [TeamB] wrote: ... > compile without a lot of changes. ... I have used WinForms for a while, but was really glad I could go ...
    (borland.public.delphi.non-technical)
  • Re: What bothers me...
    ... fixes the performance issues with WinForms. ... Craig Stuntz [TeamB]. ...
    (borland.public.delphi.non-technical)
  • Re: Is VCL dying yet?
    ... Rudy Velthuis [TeamB] wrote: ... Unless the .NET runtime was ... WinForms, calling into the 64 bit OS. ...
    (borland.public.delphi.non-technical)