Re: Delphi as a Career Choice in the United States
From: Dennis Landi (nada_at_nada.com)
Date: 10/05/04
- Next message: Dennis Landi: "Re: Delphi as a Career Choice in the United States"
- Previous message: Rudy Velthuis [TeamB]: "Re: Delphi as a Career Choice in the United States"
- In reply to: Larry Drews: "Re: Delphi as a Career Choice in the United States"
- Next in thread: Larry Drews: "Re: Delphi as a Career Choice in the United States"
- Reply: Larry Drews: "Re: Delphi as a Career Choice in the United States"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 5 Oct 2004 15:58:48 -0400
"Larry Drews" <ldrewsNOSPAM@tampabay.rr.com> wrote in message
news:Xns95799E10178B0ldrewstampabayrrcom@207.105.83.66...
> For you the answer may be to abandon Delphi for some other toolset. If
so,
> then please do it and get on with life. If you plan to stick with Delphi,
> then please start coming up with some useful suggestions to improve the
> situation. If you are not willing to do either of the above, then please
> just keep quiet and let the rest of us do what we can without having to
> contend with incessant whining.
>
Actually although I prefer the term "advocacy" and "agitation" over
"whining" (they are all just "words" after all), I do think what you said is
fair.
Larry, don't think I am not listening when you come on this forum with the
deliberate intent to say something NICE. I am sure we are all listening.
However, some are listening more intently (and CRITICALLY then others).
But tell me Larry, how does the revelation that Borland's sales force hasn't
been actively selling Delphi since 1997 affect you? I would really like to
know. I am obviously much younger than you, but I am also a consultant who
has worked hard to get Delphi in the door where ever I could for the past
ten years (yes, a mere fraction of your forty, I grant you). I respect
forty years doing anything, but that doesn't mean I am going to suspend my
faculties for critical analysis just to play some listless, sad cheer leader
until the lights go out.
Yes, I have my trusty Win32 Delphi code and I love it. There is a clear
and available path to continue using that code into the future (Win64); and
I fully expect my vendor to what it can to protect my investment. If the
vendor doesn't take that path and If I have to scrap this code, than the
covenant is broken. I am free to choose my next code base altogether
unemcumbered by the past.
Let me come up with a heart felt list for you off the top of my head and you
can play Good Cop to my Bad Cop:
Choosing my next platform will have to take in factors such as
- how well a prospective vendor takes care of its customers over time,
- how well the vendor treats its (vital) 3rd Party developer community;
- how well the vendor treats its independent 3rd Party Authors and Tech
Writers;
- the robustness,
- performance and
- breadth/depth of functionality offered,
- its penetration in the market place, presently,
- its chances of gaining a robust presence in the market place of the
future given the inevitable customer base attrition inevitable with any
product...
Since we know that the writing is on the wall for Win32, Larry, I would like
to hear your opinion on what your next platform will be and how it stacks up
against the above list of criteria. If you think some criterion is bogus,
feel free to say why. If I've missed a criterion, feel free to add it to
the list.
This isn't a trap. Please feel free to be as positive as you like.
-d
- Next message: Dennis Landi: "Re: Delphi as a Career Choice in the United States"
- Previous message: Rudy Velthuis [TeamB]: "Re: Delphi as a Career Choice in the United States"
- In reply to: Larry Drews: "Re: Delphi as a Career Choice in the United States"
- Next in thread: Larry Drews: "Re: Delphi as a Career Choice in the United States"
- Reply: Larry Drews: "Re: Delphi as a Career Choice in the United States"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
