Re: Delphi to Visual Studio Conversion Project

Jan Derk a écrit :

The previous post too was sponsored by Microsoft Visual Studio...

Do I wish! I even have to pay for my own copy.

Joking aside. You are not the only TeamBer doing this. In many posts you
promote C# or Visual Studio. Why - as a TeamB member - would you do that?

Not so much promoting it but, when you are forced to move away from Delphi (in the dark years) 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.

In my humble opinion it hurts CodeGear in a terrible way. You obviously are
mainly working with CodeGear's biggest competitor and often mentioning its
advantages or telling reasons why you moved projects from Delphi to C#.

If you read through my post, you will see that, at the end, I state that, had Delphi been somewhere near where it is now, we would more than likely have stayed with the IDE and language, but we would have moved to ..NET for the excellent frameworks it provides.

Most here will disagree with your preference for .NET. If I would not think
that native Delphi is the still king for creating mean and lean applications I
would not hang around here. The problem is that those in doubt if Delphi is the
best choice for them may read your (because of the TeamB title) authoritative
MS promotion and another sale is lost. I am hoping that CodeGear will stay
alive until they bring us Unicode and win64 support and your posts are not
helping.

I too am hoping that CodeGear stay alive as, without them around, MS could well get complacent, thinking they are the only game in town. However, as others have said, trying to catch up with the company that makes the rules is no easy matter.

As to whether .NET is a "good thing"tm or not, I use it, and would use it in Delphi if necessary, not because it is an MS product but because it really seems to be everything that the VCL should have been and hopefully, one day, will become.

Now, the rumour is that .NET features like generics will become a part of Delphi for Win32. It was for the features that the .NET framework provided over and above VCL that I moved to .NET. It just so happened that, at the time, Borland was spending too much effort killing the golden goose rather than getting on with feeding it on the new "food" available.

This is no criticism, just curiosity. And maybe I am the only one here
wondering why you (and some other TeamBers) are doing this.

TeamBers are not CodeGear employees, they are usually consultants or developers who have to make a living out there in a big harsh commercial world. For some of us, that living has to be made in other languages or IDEs. That does not stop us being ardent supporters of CodeGear, especially as we tend to regard some of the developers there as friends rather than simply anonymous faces.

My speciality is not just writing code, it is designing OO systems and implementing them in code. As to what language or IDE I use, that is usuallydown to the company for whom I am doing the designing. Maybe you are in the fortunate position of being able to choose to work in Delphi, but some of us do not have that luxury.

I hang around in these groups to fulfil my TeamB responsibilities of monitoring them, but also to be available to offer help and advice on OO design issues where needed. Now, if any of you have a will, the time and money, then you too could bring the Delphi Win32 VCL up to the same kind of functionality that can be found in .NET. Should you want any advice on how to design a better VCL, then I am available, but beyond these groups, I have to make a living so, if you have a spare pot of cash around, I could be all yours (and Delphi's) :-)

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 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)
  • Re: More fuel for the 64-bit fire ...
    ... Rudy Velthuis [TeamB] wrote: ... > Perhaps because Delphi is not just a compiler (of which we don't know ... > framework like the VCL, which may be a lot of work to port and test. ...
    (borland.public.delphi.non-technical)