Re: usual nontechnical issues

From: Atmapuri (janez.makovsek_at_usa.net)
Date: 11/25/03 

Date: Tue, 25 Nov 2003 22:03:53 +0100

Hi!

> 12. What people like about Delphi is IDE and components.

Actually, I think the compiler is also nice.. In 1995 it was revolutionary.
A merger between VB and C++. The good components are only
a consequence of the compiler excellence. Todays Delphi
component market reflects how well Borland did its job
with the compiler and the IDE.

Without good ground to grow on, even best component writer cant flurish.
I still think that W32 Delphi today has a component base that beats .NET's
by far. The only Delphi downside is that it is not from Microsoft.

> 13. Why not drop Delphi now, and focus on C#Builder, JBuilder, and CBX. I
can
>see same IDE backed up with UML designer. Bundle C#, Java and C++ under
same IDE
>and tools envelope, and drop compilers. Sun is doing Java, Ms is doing net,
and Intel,
>Microsoft and open source community are doing C++.

Well. If you continue dropping things instead of making them sell...
What is then left of the company? You are also forgetting that:

- Others are doing free IDE.
- Others are doing free tools...also...

There was a big discussion on the new CBX IDE. For a W32 developer
its only a little better then most of the freely available C++ IDE's
floating
around. It makes almost no sense to buy CBX for its IDE. Besides,
the CBX's component framework is public property. What is there
to sell, if it is free anyway? Borland says it will make it better, but
hey...
you are running against the free tools on the same playfield...

That's a little harsh...

Borlands basic idea was:
make the compiler, IDE and tools and make each of this elements
so much better that you will be able to beat the competition bad. Delphi
was succeding in this for at least 6-7 years.

Considering constant pressure from Microsofts monopol, Delphi
could not have survived, if it really did not offer something substantially
better.

Then from 2000 on Borland made a series of mistakes.
Delphi development team was doing Kylix, web services
UML. It failed to realize the threat of .NET. The need
was to vastly improve the IDE and the compiler, to keep
its overall superiority over VS .NET

Instead, the developed components aged out and the
compiler and the IDE, the Delphi "core", the real long term investment,
were starving...

We will now get Delphi 8 with new IDE and new compiler.
One year too late and not as superior as they could have
been by now.

Luckily, there is still time before next Windows version in 2006.
It may be true now, however, that more resources will be
neccessary, to put enough juice in to development of
all the key parts of Delphi: IDE, compiler and tools.

Its only when you do all the three things right, you can get
something really substantially better.

Regards!
Atmapuri.

Relevant Pages

  • 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: Why arent you upgrading?
    ... Stable IDE - this is first and foremost before anything else. ... MS alternate choice - As I see it the reason Delphi became so ... better database support ... Then announce that 64-bit native compiler is in progress and started. ...
    (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)
  • Delphi - does catastrophe loom ? (long)
    ... I've been buying and using Delphi since Turbo Pascal 5, and think that it is the ... However, I am beginning to think that Borland has made a major mistake going down the .NET path, and that Microsoft will be the beneficiary. ... however, when a 64-bit compiler was first mentioned at Borcon 2002 in Australia, it was targetted solely at Itanium. ... What Borland Marketing does not seem to comprehend is that while the market for an IA-64 compiler was probably several tens or even hundred of units, the market for an AMD64 compiler is in the range 10^4-10^5 units. ...
    (borland.public.delphi.non-technical)
  • Re: Future of Delphi 7.x - need official word from Borland
    ... of the IDE is Borland innovation. ... The Delphi for .NET compiler is entirely Borland's design as it compiles ... The language has evolved with much more than just that, ... So retro-fitting new .NET language features into the Win32 compiler doesn't ...
    (borland.public.delphi.non-technical)