Re: Delphi to Visual Studio Conversion Project
- From: "Patrick Moloney" <NewsID*at*SandrockSoftware.c*o*m>
- Date: 31 Dec 2007 05:22:42 -0700
Wayne Niddery (TeamB) wrote:
You're reading something that isn't there. They state two objectives
- 1. Move from client/server to 3-tier and 2. Move to VS/C#. Either
could be done without the other, there is no implication at all of
scalability problems in Delphi.
Wayne, thank you, you've hit the nail on the head.
I'm reading this long thread thinking everyone has missed the point
here. And, I believe most would accept the conventional wisdom that
n-tier is more flexible, scalable and some other things - whatever
language it is written in. So, that has nothing to do with the language
- Delphi or otherwise.
It's a pity that some IT managers, or whoever, jumble all things
together and suggest:
1. Total Re-writes
2. Re-architect to N-Tier
3. Built with MS tools
4. Commitment to dot Net
That's a lot of change. I would hope they are forced to do a lot of
justification for each of these individually with more conviction than
the options of what else might be done in the future. It's no wonder
IT projects are over budget, late and short on functionality.
--
Patrick Moloney
.
- References:
- Delphi to Visual Studio Conversion Project
- From: Anonymous
- Re: Delphi to Visual Studio Conversion Project
- From: Wayne Niddery \(TeamB\)
- Delphi to Visual Studio Conversion Project
- Prev by Date: Re: Delphi to Visual Studio Conversion Project
- Next by Date: Re: Delphi to Visual Studio Conversion Project
- Previous by thread: Re: Delphi to Visual Studio Conversion Project
- Next by thread: Apache Pascal Module
- Index(es):
Relevant Pages
|