Re: Captain Jake's Top Ten List of what I'd like to see inthenextversionof Delphi
- From: Brian Moelk <bmoelk@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 29 Jun 2006 17:37:24 -0400
John Jacobson wrote:
I would prefer it to being stuck in a very old version of Delphi simply because
it would cost a substantial amount of money to upgrade the components used.
I've never thought the upgrades were substantial. I always weigh them
against how much time would it take to develop/maintain/test this
ourselves...
Besides, approximately what overall cost are you looking at? 500? 1k? 3k?
If they offered free upgrades it wouldn't be an issue. But they don't.
Many of them license their source code for just a bit more. Others
offer subscriptions.
Many of
them charge a lot for upgrades,
They do? Most offer discounted upgrades.
so that upgrading Delphi becomes a major
expense that is then priced right out of reality for most corporate development
shops with substantial pre-existing code bases.
For corporate development shops, upgrading tools is always a large
expense; most of which is in human resources having to deal with
testing, time lost due to the upgrade of tools, etc.
Your assumption here strikes me as very short sighted.
There are a lot of shops that
are looking at the cost of upgrading Delphi and comparing it to the cost of
simply moving to Visual Studio, or staying with their current version of
Delphi. The third-party components are like a millstone around Delphi's neck in
such comparisons.
VS.NET has it's own upgrade issues; they aren't immune from these
problems.
Regardless, reliance on third-party components is a development choice
and there are advantages/disadvantages to the whole build/buy argument.
IMO, if someone walks into the "buy" option without considering upgrade
costs, that's just foolish.
I do not believe backward compatibility of dcu's will help in any
substantial way to make the "buy" argument more appealing. The solution
is really simple: when buying a component, buy the source code edition.
--
Brian Moelk
Brain Endeavor LLC
bmoelk@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
.
- Follow-Ups:
- Re: Captain Jake's Top Ten List of what I'd like to see inthenextversionof Delphi
- From: Don Strenczewilk
- Re: Captain Jake's Top Ten List of what I'd like to see inthenextversionofDelphi
- From: Jon Robertson
- Re: Captain Jake's Top Ten List of what I'd like to see inthenextversionofDelphi
- From: Jolyon Smith
- Re: Captain Jake's Top Ten List of what I'd like to see inthenextversionof Delphi
- References:
- Captain Jake's Top Ten List of what I'd like to see in the next version of Delphi
- From: Captain Jake
- Re: Captain Jake's Top Ten List of what I'd like to see in the next version of Delphi
- From: Brian Moelk
- Re: Captain Jake's Top Ten List of what I'd like to see in the nextversion of Delphi
- From: Nick Hodges (Borland/DevCo)
- Re: Captain Jake's Top Ten List of what I'd like to see in the nextversion of Delphi
- From: John Jacobson
- Re: Captain Jake's Top Ten List of what I'd like to see in thenextversion of Delphi
- From: Brian Moelk
- Re: Captain Jake's Top Ten List of what I'd like to see in thenextversionof Delphi
- From: John Jacobson
- Captain Jake's Top Ten List of what I'd like to see in the next version of Delphi
- Prev by Date: Re: Captain Jake's Top Ten List of what I'd like to see in the next version of Delphi
- Next by Date: Re: Captain Jake's Top Ten List of what I'd like to see inthenextversionofDelphi
- Previous by thread: Re: Captain Jake's Top Ten List of what I'd like to see in thenextversionof Delphi
- Next by thread: Re: Captain Jake's Top Ten List of what I'd like to see inthenextversionofDelphi
- Index(es):
Relevant Pages
|
|