Re: ECO, Delphi, Codegear, and CapableObjects (Delphi for VS!)
- From: Brian Moelk <bmoelk@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 12 Jul 2007 12:56:29 -0400
Nick Hodges (CodeGear) wrote:
I don't believe we are a technology company. I believe we are a
solutions company. I believe we should focus on providing solutions to
customers issues. I don't believe we should be spending our time
chasing around every new technology.
IMO, you should be *creating* new technology not *chasing* others
technology. That's what it means to be a technology company rather than
a solutions company.
I'm not advocating recreating the wheel, what I'm advocating is
producing something better and in order to do that sometimes you've got
to create new technology.
If you see CodeGear as a "solutions" company, I suspect you'll end up as
IDE plug-in vendor rather than one that creates their own compilers and
framework technologies.
One of the reasons that we
shouldn't be doing that is because we can't. We have to focus. We are
focusing on providing solutions for Delphi developers. We aren't going
to be able to cover the enourmous pile of spaghetti that other
companies have thrown against the wall trying to get it all to stick.
I agree wholeheartedly with that, but you're missing the point. Delphi
shouldn't be everything to everyone, it can't be. It never was anyway.
But CodeGear has to commit Delphi to a certain technology stack at the
end of the day. Historically it's been a Windows tool and Delphi has
done very well with that.
The problem is that I believe Delphi can no longer remain a Windows-only
tool because MS has raised the bar. Both in terms of quality and scope.
Delphi must forge it's own identity while remaining true to its heritage.
IMO, the way forward is to embrace native code development, but expand
it across platforms like Kylix did. Go after OSX, go after Linux but do
it with server applications, go after Windows Mobile but do it with a
native compiler. Create a next-gen GUI framework using OpenGL, don't
piggy back on a partial WPF VCL hack. Create a nice ORM/inversion of
control framework that is based on native code, not managed code.
These are the kick ass things that I believe Delphi developers really
want...not some half baked "solutions" that require the same mess of
technological dependencies that MS tools do.
If I simply want solutions, I wouldn't use CodeGear's.
Okay. Fair enough. That's totally up to you. Many others feel
differently.
Yes, cults have quite a large followings.
No --- but we build clients. A customer needs a client application,That's complete and utter crap.
and we provide an excellent solution for them.
Nice chatting with you, Brian.
You asked, I'm being as direct and honest as I can. If you can't handle
being called out in that way, then don't ask me what I think, because I
think your answers are exactly that: utter crap.
IMO, it's a shame that a little tough language makes you run away from
or perhaps gives you an excuse to ignore the rest of a post that I tried
to write in a thoughtful manner.
--
Brian Moelk
Brain Endeavor LLC
bmoelk@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
.
- Follow-Ups:
- Re: ECO, Delphi, Codegear, and CapableObjects (Delphi for VS!)
- From: Sergio Sette
- Re: ECO, Delphi, Codegear, and CapableObjects (Delphi for VS!)
- References:
- ECO, Delphi, Codegear, and CapableObjects
- From: Nick Hodges (CodeGear)
- Re: ECO, Delphi, Codegear, and CapableObjects
- From: Kyle A . Miller
- Re: ECO, Delphi, Codegear, and CapableObjects
- From: Wayne Niddery [TeamB]
- Re: ECO, Delphi, Codegear, and CapableObjects
- From: Kyle A . Miller
- Re: ECO, Delphi, Codegear, and CapableObjects
- From: Wayne Niddery [TeamB]
- Re: ECO, Delphi, Codegear, and CapableObjects (Delphi for VS!)
- From: Kyle A . Miller
- Re: ECO, Delphi, Codegear, and CapableObjects (Delphi for VS!)
- From: Eddy Poullet
- Re: ECO, Delphi, Codegear, and CapableObjects (Delphi for VS!)
- From: Kyle A . Miller
- Re: ECO, Delphi, Codegear, and CapableObjects (Delphi for VS!)
- From: Bruce McGee
- Re: ECO, Delphi, Codegear, and CapableObjects (Delphi for VS!)
- From: Kyle A . Miller
- Re: ECO, Delphi, Codegear, and CapableObjects (Delphi for VS!)
- From: Bruce McGee
- Re: ECO, Delphi, Codegear, and CapableObjects (Delphi for VS!)
- From: Kyle A . Miller
- Re: ECO, Delphi, Codegear, and CapableObjects (Delphi for VS!)
- From: John Moshakis
- Re: ECO, Delphi, Codegear, and CapableObjects (Delphi for VS!)
- From: Kyle A . Miller
- Re: ECO, Delphi, Codegear, and CapableObjects (Delphi for VS!)
- From: Nick Hodges (CodeGear)
- Re: ECO, Delphi, Codegear, and CapableObjects (Delphi for VS!)
- From: Brian Moelk
- Re: ECO, Delphi, Codegear, and CapableObjects (Delphi for VS!)
- From: Nick Hodges (CodeGear)
- Re: ECO, Delphi, Codegear, and CapableObjects (Delphi for VS!)
- From: Brian Moelk
- Re: ECO, Delphi, Codegear, and CapableObjects (Delphi for VS!)
- From: Nick Hodges (CodeGear)
- Re: ECO, Delphi, Codegear, and CapableObjects (Delphi for VS!)
- From: Brian Moelk
- Re: ECO, Delphi, Codegear, and CapableObjects (Delphi for VS!)
- From: Nick Hodges (CodeGear)
- ECO, Delphi, Codegear, and CapableObjects
- Prev by Date: Re: International Pricing Policy
- Next by Date: Re: ECO, Delphi, Codegear, and CapableObjects (Delphi for VS!)
- Previous by thread: Re: ECO, Delphi, Codegear, and CapableObjects (Delphi for VS!)
- Next by thread: Re: ECO, Delphi, Codegear, and CapableObjects (Delphi for VS!)
- Index(es):
Relevant Pages
|