Re: What I Think Delphi Needs to Do to Survive

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.

Lauchlan,

How many people do you suppose find that the syntax is the overriding
reason to use Delphi? The libraries and practices in developing a
platform are FAR harder than learning a different syntax. There's a
small comfort level issue in language familiarity, but I'd argue that
my BRIEF keymap is harder for me to part with than ObjectPascal Syntax.
That's why Chrome isn't gonna get a lot of converts. Because it brings
almost nothing to the table aside from a different syntax.

Randy
.

Relevant Pages

  • Re: Delphi? Futureproof re vb!
    ... .NET side of things over the older syntax side. ... Delphi experience will be along to address these issues. ... Apparently dot net express is an attempt by Microsoft to get back ... to the vb6 concept which they should never have left! ...
    (microsoft.public.vb.general.discussion)
  • Re: Delphi refocussing on .Net - good or bad?
    ... And conversely, if shared source is a valuable thing, doesn't this throw a big monkey wrench for those that wish to have common source libraries for both native and .NET platforms? ... the majority of the remaining Delphi developers are interested in native solutions, ... many Delphi developers interested in .NET development have moved to C# or Oxygene or something else. ... It's completely spinning CodeGear's past choices as reasonable, when I would bet that nearly all objective measures of revenue, marketshare, ROI, etc. indicate that those choices were poor ones. ...
    (borland.public.delphi.non-technical)
  • Re: Delphi refocussing on .Net - good or bad?
    ... But without betraying confidential discussions with MS it's safe to say that we had very good reason to believe that new APIs would increasingly be only released managed, and that Win32 C APIs would become legacy only. ... Does Delphi become obsolete and "restricted" to only the old Win32 APIs and only a Win98/XP dev tool? ... Thunking solutions were considered but that would ultimately still leave Delphi apps and developers as second tier citizens on Windows. ... Building a solid .NET capability without abandoning native code was something we had to do in order to be sure that Delphi developers would not be left out of the future Windows technologies. ...
    (borland.public.delphi.non-technical)
  • Re: The Delphi Survey
    ... Yes, Delphi is a fantastic development tool for Windows and deserves a future, but the future is not only Windows is is fast becoming Linux as well.. ... However most Delphi developers feel comfortable with the knowledge that there is a backup deployment possibility - this is also how most developers 'used' Kylix - the safety net on the shelve. ... IOW to sell more of Delphi you need a cross platform strategy on the roadmap - a win win scenario. ...
    (borland.public.delphi.non-technical)
  • Re: newie. Any pointers?
    ... I ve been developing software for the last 3 or 4 years with delphi ... syntax changes (note that mapping your delphi library knowledge is not going ...
    (microsoft.public.dotnet.framework)