Re: What I Think Delphi Needs to Do to Survive

Actually, my track record on these types of things has been pretty
good. For example, I predicted that Aristocrat would kill TurboPower.
I predicted that Chrome would not be a big commercial success or
challenge Delphi in any way in the market.

I missed the whole TurboPower death (except noticing when it happened).
But as far as Chrome, I don't think you needed to be a genius to know
the future there. Chrome is always going to be a niche product. I
always felt that trying to divorce the ObjectPascal language from all
things Delphi (VCL, the IDE, etc) was a losing proposition. A language
is just a language, and there's no real language-based reason to pick
ObjectPascal over C# or VB.NET. RemObjects doesn't seem to understand
that. (not that they haven't done a few nice things to the language -
but not enough to actually cause people to move to their tool).

Hmm. With respect to Jake's comments, I'd say 'over what timeframe'? It's
conceiveable (although I don't think it's likely) that after Delphi is sold,
it gets sold again, and discontinued. Maybe afterwards, Delphi developers go
to VS.NET, and choose Chrome with it, and Jakes predictionbecomes clearly
falsified. Who knows? Anyway, my point is that you can't evaluate
predictions like this until something happens to clearly establish final
outcomes (e.g. RO or Delphi being discontinued) and that hasn't happened and
hopefully won't happen.

With respect to your comments, of course Chrome is going to be a niche
product. There is no conceivable way they are going to put MS out of
business, for example, as they provide essentially an add-in for VS.NET.
Therefore by definition they occupy a niche. But maybe it's a good niche to
have? Who knows, it depends on their business case, revenue and costs.

Lauchlan M


.

Relevant Pages

  • Re: Chrome unveiled to the public
    ... > should be crazy NOT to do it in Chrome... ... to rewrite JSN in .NET. ... I think at work if we did go to .NET, we'd either stick with Delphi or go to ... I've heard is that I'd get to use a very nice language if I wanted. ...
    (borland.public.delphi.non-technical)
  • Re: Why arent you upgrading?
    ... Not because of the language, ... Chrome is different from C#, and offers some features C# doesn't offer. ... Without rehashing all of the specific issues regarding Delphi for .NET, ... about vision and understanding what is going to serve your customers ...
    (borland.public.delphi.non-technical)
  • Re: Delphi within Visual Studio?!?!
    ... Chrome isn't intended to be a general purpose ... >> programming language? ... As for question, the statement that 'Delphi and Chrome ...
    (borland.public.delphi.non-technical)
  • Re: How would you steer Delphi if you were Nick?
    ... language like Object Pascal ... But Delphi Object Pascal. ... Have you looked at the Chrome variant of Object Pascal? ... the Delphi language was great for Win32 apps - it made ...
    (borland.public.delphi.non-technical)
  • Re: Delphi 2005 Truly Unsuable for Your Testing and QA Too?
    ... Exhibit 2 from thread: Is VCL.NET becoming the golden egg of Delphi - ... >Is VCL.NET a Delphi technology that won't work on Chrome? ... >I find it unsurprising that marc disses VCL.NET, ...
    (borland.public.delphi.non-technical)