Re: Delphi to Visual Studio Conversion Project

GC I can understand, though I dislike it myself, having seen machines come to a dead stop while the GC did its thing, then resume again (this was probably 20 years ago, so I'm sure it's improved greatly).

But other than GC, why choose C# over CBuilder? Is there an advantage of generics over templates that I'm missing? I'm not a professional in C++ if you haven't already figured that out, but can hold my own. For your resume, perhaps (not meant as an insult; wish I had more VS stuff on my resume, but I really don't like MS tools)?

"Joanna Carter [TeamB]" <joanna@xxxxxxxxxxxxx> wrote in message news:4777fd3a$1@xxxxxxxxxxxxxxxxxxxxxxxxx
Anonymous a écrit :

Found this on the guru.com website. Any comments on the wisdom of a conversion like this? Cost vs. staying with Delphi? Is there really a scaling problem that VS can handle that Delphi can't?

Apart from changing to the "flavour of the month" IDE, even thouhg I use and love VS and C#, this seems like folly to me. There really isn't that much more, within the remit given, that Delphi can't handle. Before choosing C# for things like generics and GC, we had a multi-tier app completely written in Delphi with no problems at all.

Joanna

--
Joanna Carter [TeamB]
Consultant Software Engineer

.

Relevant Pages

  • Re: Delphi to Visual Studio Conversion Project
    ... I'm not a Delphi person; my preference is CBuilder, so I don't really know the answer to my own question. ... but I do know about piss poor management and that was my first thought; it's a management decision and you're stuck with it. ... Is there really a scaling problem that VS can handle that Delphi can't? ...
    (borland.public.delphi.non-technical)
  • Re: Delphi to Visual Studio Conversion Project
    ... Cost vs. staying with Delphi? ... Is there really a scaling problem that VS can handle that Delphi can't? ...
    (borland.public.delphi.non-technical)
  • Re: Delphi to C#?
    ... to get pseudo-templates for Delphi. ... .NET generics are just so well designed and much more ... statement that populated an entire TChart bar chart with one query: ... is awkward. ...
    (borland.public.delphi.non-technical)
  • usual nontechnical issues
    ... Although I'm not usually initiating "future of Delphi" threads, I have need to share some thoughts and hear oppinions. ... There is no way to justify Kylix usage with enterprise applications. ... VCL is about to be dead. ... Borland said that, and I agree, there is no need to maintain VCL in future, because .net framework is there. ...
    (borland.public.delphi.non-technical)
  • Re: Delphi roadmap from the .NET perspective...
    ... If I were banking VB many many years ago, when we've decided to use Delphi ... I've successfully ported some COM+ server applications to .NET WebServices ... We just don't know either if in 3 or 4 years MS will screw some developers ... I face LINQ like I face generics. ...
    (borland.public.delphi.non-technical)