Re: Captain Jake's Top Ten List of what I'd like to see in thenextversionof Delphi

"Hannes Danzl[NDD]" <hannes@xxxxxxxxxxxxxxxxxxx> wrote in message
<xn0eo35ak12kw97008@xxxxxxxxxxxxxxxxxxxxxx>
That is exactly the mindset that is creating for any thirdparty component
developer. Buy once, use forever. You're ready to pay for a new IDE to make
your life easier, nicer, fancier, whatever.

Not always. I never bought Delphi 7, for example. My current employer never
moved up from Delphi 6, for another example. I'd love to use D2006 at work, but
for that to happen we'd have to buy a new version of the entire DevExpress set
of components since we have only the DCU version, in addition to the
substantial costs of D2006 itself, as well as a few other components. That
makes an already difficult sell even harder.

You're ready to invest time to
move your projects over (and please don't tell us that it won't take any
time).

When I moved my newsreader over to D2006 I remember it taking only about a day,
because I had bought the source code to any third-party components I was using.
My philosophy in my personal programming projects is to use only those
component for which I have the source. However, I have no such control over
firms in the market for a Delphi developer. More often than not we get pulled
into a project that was started a long time ago and built according to a design
philosophy that may be quite different than our own.

At the same time you now expect the other 3rd party companies to invest
that time too (and believe me its MUCH more involved than you think: code
changes, testing, IDE integration changes and oh, did i mention testing?). Now
there's the problem: you expect them to deliver that free of charge forever?
Seriously do ou have any idea how much time is involved in e.g. still
supporting D5 and D6?

I don't expect them to furnish anything past the version I purchase. I would
like for that version to work through the next several versions of Delphi. I
would also like to be able to use a new version of Delphi without having to buy
new versions of components, because, quite frankly, at most employers it simply
is not going to happen if it costs too much.

For my personal programming, I can easily upgrade to the latest version of
Delphi Pro.


A non changing DCU format won't help here. The RTL is *always* going to
change, thus all other units' dependencies/interfaces have to be checked. The
testing wouldn't be taken away anyways, cause there will also alway be slight
changes in functionality somewhere in the RTL or VCL you rely on.

There is a principle of good design that says you never change or delete parts
of an already-published interface, you simply add new non-conflicting
functionality. If you follow this rule, you greatly minimize the need to
re-test everything that is built on a particular interface just because you add
new functionality.

--
***Free Your Mind***

Posted with JSNewsreader Preview 0.9.4.2586


.

Relevant Pages

  • Re: Ouch!
    ... If you've bought delphi from 2-6 ... the worst out-of-the box experiences I've had from borland. ... version Delphi you've owned previous to this. ... The IDE AVs every time I try to close a project. ...
    (borland.public.delphi.non-technical)
  • A good DELPHI book?
    ... I am a totally newbie in DELPHI (I haven't still ... bought the IDE :-)) and I want to decide ... My project involves a lot of custom drawing, ...
    (comp.lang.pascal.delphi.misc)
  • Re: Delphi 2005 update 1 is out!
    ... Delphi 2005 Update 1 Fixes ... When importing an assembly if the types Pointer or Exception are used ... bdpDataAdapter can cause the IDE to lose all key stroke events until ... Using a remote data module may cause an Access Violation. ...
    (borland.public.delphi.non-technical)
  • Re: Delphi Update one... are you serious?
    ... Delphi 2005 Update 1 Fixes ... When importing an assembly if the types Pointer or Exception are used ... bdpDataAdapter can cause the IDE to lose all key stroke events until ... Using a remote data module may cause an Access Violation. ...
    (borland.public.delphi.non-technical)
  • Re: Why arent you upgrading?
    ... Stable IDE - this is first and foremost before anything else. ... MS alternate choice - As I see it the reason Delphi became so ... better database support ... Then announce that 64-bit native compiler is in progress and started. ...
    (borland.public.delphi.non-technical)