Re: Delphi to Visual Studio Conversion Project

Jan Derk a écrit :

Let me make it clear that I am not anti .NET or anti MS. For certain
areas .NET makes more sense (ASP.NET for example) and for others
native Delphi is the better solution (snappy scalable desktop and some
client server applications). And .NET has got an excellent framework
indeed. I myself recommend anyone needing .NET and considering
Delphi.NET to use VS C# instead.

And would I be allowed to agree with your atitude of recommending people to use VS C# for .NET development? Or is it that you have an agenda to keep Delphi "pure" and untainted by MS's .NET "virus"? :-)

Let me make my feelings plain; I personally believe that there is absolutely nothing in this world better than Delphi for Win32 development. But, when it comes to .NET, my personal belief is that Borland, as was then, did not take the bull by the horns early enough to take advantage of the early .NET momentum. Fortunately, things have changed and CodeGear seem to be doing their best to provide an alternative to the MS lock in for those who wish to or need to move to ..NET. Due to their practice of trying to maintain backwards compatibility in Delphi, it should be possible to use a single code base for both platforms. One of the results of this "compatibility", should also be the addition of goodies that were introduced into the .NET compiler.

All I tried to say is that to me it seems unwise to post so often why
for you C# is better than Delphi while wearing your TeamB name tag.

Seeing as I was invited on to TeamB to support C#, I really don't see a conflict. Just because I can't use a CodeGear IDE *at the moment* doesn't mean that I have to move back to using the Delphi language, especially as I have just invested several years in using C# for a major client.

Joanna

--
Joanna Carter [TeamB]
Consultant Software Engineer
.

Relevant Pages

  • Re: Guidelines please
    ... I used to have the opinion that team b had blind patriotism for Delphi, ... And most of my posts are answered by them first, so GO TEAMB GO ... Borland should add better Crash Support like fastMM etc but thats their ...
    (borland.public.delphi.non-technical)
  • Re: Delphi to Visual Studio Conversion Project
    ... Why - as a TeamB member - would you do that? ... Not so much promoting it but, when you are forced to move away from Delphi because of Borland's antics, it doesn't mean that you necessarily want to forsake the company and friends that you have made on the way. ... It was for the features that the .NET framework provided over and above VCL that I moved to .NET. ... As to what language or IDE I use, that is usuallydown to the company for whom I am doing the designing. ...
    (borland.public.delphi.non-technical)
  • Re: Delphi for .NET and Win32
    ... I realize, that with you doing the (TeamB) in each of your msgs, your view ... is to support and agree with everything coming out of Borland pretty much. ... But it does not truly benefit the Delphi 7 developers who purchased the ... > Rudy Velthuis ...
    (borland.public.delphi.non-technical)
  • Re: Jeff, why was my post cancelled?
    ... If the topic is Clx then either this group or the Kylix non tech (if the ... either the Delphi or Kylix Clx groups depending on which one your are having ... NOT a cross platform product. ... He'd push TeamB issues ...
    (borland.public.delphi.non-technical)
  • Re: Object Pascal Stigma, Useless Survey Question
    ... > Jeff Overcash (TeamB) wrote: ... >> You aren't going to convince schools to use ... >> Delphi to teach with unless you first convince the corporate world to use Delphi ...
    (borland.public.delphi.non-technical)