Re: Captain Jake's Top Ten List of what I'd like to see in thenextversionofDelphi



Randy Magruder wrote:

Sorry Randy, I don't believe this is about Borland's failed evangelism
or marketing. It's about Borland's failed VCL.NET strategy itself.

You haven't substantiated this at ALL.

Just what would you require to substantiate that assertion? Would the
fact that only a /tiny/ handful (IME) of the Delphi community are even
interested in using VCL.NET persuade you ? What about the ongoing chronic
(and not improving) lack of third party control support ? Maybe the fact
that by the time VCL.NET has been upgraded fully support v2.0 of .NET
(at least 14 months after the fact), version 3.0 of the framework will be
on our doorstep along with WPF and another whole clutch of the latest .NET
technologies that Delphi inevitably doesn't support but the less expensive
Visual Studio inevitably does ?

This always strikes me as crazy argument. .NET and Win32 aren't
really multiple platforms that people really care about. They are
both pretty much "windows-only" platforms. Unless DevCo embraces
mono whole hog, that's my take on it.

Microsoft will drag us kicking and screaming into .net if they have to.
This argument will be one we laugh about in 3 years time.

....and based on most current evidence, Visual Studio will be the
only game in town given the impossibility of /any/ third party
IDE vendor offering up viable, compelling alternatives in that
space while all the time desperately spinning their wheels
attempting to keep up with the endless new technology churn from
Redmond. IMO, back in the old days, if Microsoft had owned the VCL
the way they own the FCL, Delphi would have died sometime around,
oh, let's say, 1997 at the latest.

..NET is a dead end for Delphi. The writing is on the wall and it
has been so for /way/ too long now. DevCo have to get off that road
and go where the beast /isn't/ going. There are people out there
that want alternatives to .NET and these people are Delphi's natural
constituency, IMHO. Everyone else has either left or is going some
day sooner or later.
.



Relevant Pages

  • My thoughts about Delphi and its future
    ... I only mention the Pascal part of Delphi because ... Cross-platform support. ... VCL framework is in my opinion the single most ... UI controls haven't changed since the beginning. ...
    (borland.public.delphi.non-technical)
  • Re: TChart questions
    ... For some Delphi versions there's an editor help available, ... Steema Support Central ... We wouldn't have even looked at TChart without it. ... If I'm doing a bar graph, side by side, two series, I get the chart ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: How would you steer Delphi if you were Nick?
    ... realistic - .NET applications are going to be developed using Visual Studio ... which is why I think Delphi will become ever more niche. ... and I'd push forward with Win64 support. ... If DevCo wants to support another platform, I would support the Mac. ...
    (borland.public.delphi.non-technical)
  • Re: Wild speculations about the "other" factors
    ... There was only ONE .NET "focused" release, Delphi 8. ... Delphi 9 had Win32 support. ... Do you think that providing as many new features of D9 ... to the Delphi/Win32 personality came without cost? ...
    (borland.public.delphi.non-technical)
  • Re: DONT USE PIXEL TRANSLATIONS IN DELPHI
    ... Bait-and-switch is when a company deliberately advertises one ... that they don't officially support ... If you honestly wanted an assurance that it would work under Delphi, ...
    (borland.public.delphi.thirdpartytools.general)