What I Think Delphi Needs to Do to Survive
- From: "Captain Jake" <nospam@xxxxxxxxxx>
- Date: Thu, 9 Mar 2006 15:57:21 -0600
Since everyone seems to be weighing in on the topic of what DevCo ought to
do, I'd thought I join the party, late. (Hang on, while I get off the short
bus...)
Unlike most Delphi enthusiasts here, I think Delphi will be operating under
significantly reduced resources in the future, and so some things must go. I
think .NET ought to go. Not because I think Borland has done a poor job
here, but because it simply is not going to be a profitable venture as long
as the 800lb gorilla is sitting on the market. Challenging MSFT seems a bad
business policy, just ask Phillippe Kahn. Unless DevCo is contractually
obligated to support .NET, they ought to cut their losses there and run.
Let's face it. For better or worse, developers wanting to do .NET
development are using VS.NET, because it gives them what they want in a
reasonable timeframe, and they will continue to use it. Tools from the
company that makes the development framework used will always dominate,
unless the alternatives are truly stellar. I honestly don't think investors
are going to give DevCo what it would need to do this right.
On the other hand, if DevCo were to decide that native support would be the
thing to drop, they will lose their one chance at a unique niche in the
market. There is a LOT of existing native code and if DevCo can breathe new
life into this code, it can create a sustainable business model, especially
if it simplifies the process of using this code from new .NET code in
VS.NET, with something much easier to use than raw C++/CLI. This would let
companies use a mix-and-match model for software development. This would
appeal to MOST businesses.
So, here is my wishlist, which is tempered by the above expectations:
1) Native support for multiple operating systems, especially the latest Mac
OS. Also compact and mobile devices.
2) Easier and more thorough multithreading support across various operating
systems. With multicore chips here, apps need to be multithreaded to take
advantage of them.
3) Unicode VCL. It's a global world. The VCL needs to adapt to this fact.
4) VS.NET add-in for easily using native code from new .NET code.
That's it. Sure there are scads of ther things I would love to see Delphi
do, but I think the above things are both necessary and sufficient for
Delphi to thrive and survive. I also think they are realistic goals for a
reduced staff of very talented individuals trying to help worried investors
recoup their investment.
.
- Follow-Ups:
- Re: What I Think Delphi Needs to Do to Survive
- From: Brian Moelk
- Re: What I Think Delphi Needs to Do to Survive
- From: Lurkio
- Re: What I Think Delphi Needs to Do to Survive
- From: Eric Grange
- Re: What I Think Delphi Needs to Do to Survive
- From: Mike
- Re: What I Think Delphi Needs to Do to Survive
- From: Jan Goyvaerts
- Re: What I Think Delphi Needs to Do to Survive
- From: Brad White
- Re: What I Think Delphi Needs to Do to Survive
- From: Mike Vance
- Re: What I Think Delphi Needs to Do to Survive
- From: Lauchlan M
- Re: What I Think Delphi Needs to Do to Survive
- From: David Clegg
- Re: What I Think Delphi Needs to Do to Survive
- From: Randy Magruder
- Re: What I Think Delphi Needs to Do to Survive
- From: Bob Swart
- Re: What I Think Delphi Needs to Do to Survive
- Prev by Date: Re: Steve Jobs very very interested.
- Next by Date: Re: What I Think Delphi Needs to Do to Survive
- Previous by thread: BDE Alternatives Guide - up for adoption
- Next by thread: Re: What I Think Delphi Needs to Do to Survive
- Index(es):
Relevant Pages
|
