Re: Controversial question re: Turbo and .Net

Michael C. wrote:

1) It's good press; It's shows that you believe in your development tool.

It is also good press to know that Delphi can be used for more than development with the Delphi language. It is extremely good press to know that Delphi plays well with other languages and other environments so you are not locked into a single solution with Delphi.

As opposed to Visual studio, where you may have multiple language support, you are definitely locked into .NET. With Delphi, you can do either, or both. Extremely beneficial! (Note that I've only played with .NET, I've done no serious work and don't plan on it anytime soon.)

2) If you provide the source, people can learn from it.

Yes. But Delphi has included third-party components without the source for years. Delphi can only include the source on things that DevCo owns or has agreements from the vendor. In some cases, you simply won't have the source code.

3) Developing in multiple languages and platforms is more unproductive than developing in 1 language and platform.

Wrong. Being able to develop in multiple languages generally makes the programmer more productive in both. And, since some people are more productive in one versus another, having the ability to mix languages so people can work in their more productive environment is not unproductive. More difficult to manage, if done poorly.

5) Delphi's language won't change. The .NET framework will continue to change. Delphi is a better foundation for continued development.

Delphi's language has changed with each release of Delphi. I'll agree that DevCo has control over the language and has zero control of .NET. But Delphi's language /will/ change.

7) Think Delphi not .NET Let's talk and develop in Delphi NOT .NET. That makes things much simpler.

For you perhaps. Although I don't know why someone else's talk of .NET causes things to get more complicated for you.

Again, I have not done anything in .NET and don't plan on it. Yet I've benefited from .NET based features in BDS. Don't weaken my development tool just because some users don't like the framework it uses.

As a professional developer, I use many tools other than an IDE. Many, many tools today are using the .NET framework. If I haven't installed it because of BDS, I've installed it because of some other piece of software.
.

Relevant Pages

  • Re: Turbo: A great idea, not properly thought through... ?
    ... currently possible under Delphi 2006. ... My experience is that people prefer one language + one ... I think it is important to get Delphi BDS away from the VS ... Seems the Turbo line misses the point in two key areas: ...
    (borland.public.delphi.non-technical)
  • Focus needs clarity and commitment
    ... Part of the point, AFAIU, is that BDS is the 'way' ... all of those additional language tools are also ... No others compete directly with Delphi, now presumably Turbo Delphi. ...
    (borland.public.delphi.non-technical)
  • Re: The Tiers of a Clown
    ... > Why would I want to add a stateless messaging layer to a typical business ... Natural, Cobol, Java, VB and of course Delphi. ... If your lucky enough to have a single language environment and plan to ... opens you up to the entire .NET Framework. ...
    (borland.public.delphi.non-technical)
  • Re: Turbo Delphi... Why ? :(
    ... language will they be using - C++, Delphi Win32, C# or Delphi .NET. ... So you will never need to use more than one language at a time? ... The thing is, BDS satisfies some of our customers needs, and Turbos ... In addition - NEW developers and students how ...
    (borland.public.delphi.non-technical)
  • Re: Over 100 Microsoft MVPs Have Signed Online Petition - Give Us Back VB!!
    ... My prime interest is *language* stability. ... "VB data controls" are com controls, ... > I wouldn't ever want to use them in Delphi - or in VB; ... My code is core to the app, business logic that is focused on the market I ...
    (borland.public.delphi.non-technical)
Loading