Re: Future of Delphi 7.x - need official word from Borland

From: Joanna Carter \(TeamB\) (joanna_at_nospam.co.uk)
Date: 01/26/05 

Date: Wed, 26 Jan 2005 14:11:56 -0000

<Erwin van den Bosch (Erwin van den Bosch)> a écrit dans le message de news:
41f790ab.18281015@forums.borland.com...

Erwin, you are exagerating on a grand scale here.

> When you install Delphi 2005 you see a lot of Microsoft stuff on you
> screen and so little Borland.

The only M$ part of the IDE you see is the .NET form designers, the majority
of the IDE is Borland innovation.

> Borland didn't even make there own .NET compiler!

The Delphi for .NET compiler is entirely Borland's design as it compiles
their own language.

> In the early days of Turbo Pascal, Object Pascal, Delphi 1 they did a
> lot of compiler/language improvements. But say since Delphi 3 nothing
> much has happened. Just small things like implementing overloading for
> example. They are only improving the Delphi IDE.

The language has evolved with much more than just that, but with the advent
of .NET, do you really think they should have invented their own syntax for
new features just to have to change them to maintain single code base
between Win32 and .NET versions of the Delphi language. Try to write single
code base VB apps, M$ had to make a clean break to move to .NET.

> But there will be no development in Borland's Win32 tools.

So retro-fitting new .NET language features into the Win32 compiler doesn't
count ?

> If you want
> to do .NET you might be better of switching to Microsoft. If you stay
> on Borland for .NET development you are depending on two tool
> builders.

You always were depending on two tool builders; or don't you remember the
problems caused by M$ changing the interfaces to the MSOffice APIs between
97 and 2000 ?

I for one really like the fact that I can develop Win32; Delphi for .NET and
C# apps in the same IDE, even debugging continuously between assemblies
written in different languages.

> I would say: So please, Mr. Kaster or someone else, please tell us
> about the future of Delphi and Borland tools.

The future is a great company doing things that M$ have never dreamed of,
let's face it they had to take on a Borlander to design .NET :-)

> Are you making that rock solid Borland tools again insteed of making
> Borland a rock solid company?

If you don't have a rock solid company then you won't be around to make
those rock solid tools.

Joanna 

--
Joanna Carter (TeamB)
Consultant Software Engineer
TeamBUG support for UK-BUG
TeamMM support for ModelMaker

Relevant Pages

  • Re: VB6, VB2005, or Something Else?
    ... up" the language rather than any requirement of the platform change. ... the site seems to have articles from Borland too. ... don't understand is that you are moving completely to Delphi. ... including a fundamental data type. ...
    (microsoft.public.vb.general.discussion)
  • Re: The Delphi Brand
    ... CG Delphi is a brand and a language. ... Meanwhile, I have recieved an email about Delphi for PHP,and ... PHP is just another programming language. ... "Borland Delphi" is a brand. ...
    (borland.public.delphi.non-technical)
  • Re: Death of Kylix and migrating towards Java
    ... But it can't beat Delphi's compiler speed! ... app developers on non-Windows platforms. ... It is NOT Delphi. ... > I do agree that Kylix was a very good promise and concept, that Borland ...
    (borland.public.delphi.non-technical)
  • Re: Delphi as a Career Choice in the United States
    ... Just about the time that Delphi 1 was ... be teaching since it was the mainstream language. ... that would also depend on Borland having the wisdom to ... Delphi programmer is about three times more productive than a C++ ...
    (borland.public.delphi.non-technical)
  • Re: usual nontechnical issues
    ... statements of Borland. ... If backwards compatibility was such a big problem, ... I am not so sure about Delphi. ... Delphi 8 for dotNet contains a brand new compiler! ...
    (borland.public.delphi.non-technical)